As a work around, try setting up field behavior so that the return exits the field. Then see if you can get the OnObjectExit trigger to work instead of OnObjectKeystroke--which has to fire and process every keystroke instead of just the "exit" event for OnObjectExit.
I've actually done that as a temporary workaround for our warehouse folks that have to scan a lot of barcodes in rapid succession.
But the underlying problem remains and can't be ignored. I didn't mention before, but the trigger script also checks for other keystrokes, such as the up and down arrow keys, to provide a convienence in record navigation. So this workaround only is good for the one specific task. I had to strip off the extra stuff out of the script.
I shouldn't have to create a workaround for behaviour that should be working (and did in a previous version).
Thank you for posting.
This issue was previously reported to Development and Testing. I've added your comments to the original report. No further information is available at this time.
Would I be correct that this occurs in Mac as well as Windows systems?
Thank you for the post.
At this time, the only reports are on Windows. The issue does not appear to occur on Mac.TSFalconFileMaker, Inc.
I believe this is a problem unique to Windows machines. On a different forum that I use others have made simular comments, but a few mention that it's (apparently) working fine on Mac systems. I wish I was able to test this out to give a good answer.