Tab Key is being fired after datachange events

I submitted an incident to the infor support portal, but I doubt it will yield any help on the issue, but it seems like there is a code difference in terms of tabbing between fields with events in version 8 versus v9+. Here is my message. If anyone has any ideas, I would appreciate it.

"Datachange events execute and complete when information is entered into a field and tabbed out of, but the tab key is still going to the next field. In my datachange event I am calling the ThisForm.SetFocus("ComponentName") inside of this datachange event, but the tab key is being executed after this event completes which renders the SetFocus ineffective. This works in version 9 and 10 of SyteLine/CSI, but in this version of 8, I cannot get this to work, I have tried losefocus and gain focus events on the field and those being tabbed into, but nothing works. Do you have any recommendations, toolset updates to fix this errant behavior, or changes to settings that might help with this issue? This is not on a vendor default form or anything like that, this is a simple custom form that allows the user to enter data on a few fields tabbing between each and firing events to perform activities. They use barcode scan guns which are programmed to pass the tab character after their scans. Without this ability to setfocus after the datachange events AND tab character, this will never function properly. "

Find more posts tagged with

Accepted answers

All comments

Stephen Cena

Have you used the "Diagnostics..." window to track what's happening with the Events? It seems odd that the same code is fine in 9 & 10 but not in 8. Though we all know 8 is "special".

Legacy Contributor

Yes, I have verified that my datachange event is ran properly when the focus out of the input field, I see my script called (I wrote out to a log text component when it is called and when it sets the focus to the next field), and I see the event complete. After it completes and I verified my script was called and the SetFocus was ran, the cursor is in the next tab order component instead of the setfocus component I called out in my script which I verified was ran and set properly. It seems that the tab portion of the input waits until the datachange event is completed to register which tabs to the next field in the tab order rather than the component called out in my setFocus. I have tried settings all components to tab order stop, disabling and/or reenabling various or all other components, but no matter what I try, the tab action simply goes to the next field in the tab order no matter what I tell it to do in my datachange event. So far, the only way I have been able to get this to somewhat focus properly is to remove the tab character from the barcode scanner and have the user click a button to manually trigger the datachange event by exiting the field instead of having the tab character perform this function. I don't know of any other character that would trigger a datachange event other than tab/shift tab. So, where version 9+ can scan A, B, C, D, D triggers an event to happen, clear the fields and jump back to A, version 8 has to scan A, B, C, D, then click this button or editable area of the form to trigger the datachange event which runs, then clears the fields and then jumps back to A. Not the worst thing ever, but certainly more cumbersome than being able to scan all day long and have the events and focus actions working in harmony.

Legacy Contributor

If there is a method for validating with a different character that doesn't jump to other fields or taking the entire input (including the tab) and edit that input stream to remove the tab character so that is triggers the datachange event but DOESN"T tab over to the next field or a setting somewhere to control the sequence of KEYBOARD ENTRY -> DATACHANGE -> TAB CHARACTER, I am all ears

wat

I'm jumping in after much prior discussion, and I haven't tested this - but perhaps you can set some variable in your code, and then put a GainFocus event call back on the next field in the tab order. You could reset the variable, and move focus to the desired place. Might work!?

Legacy Contributor

Bill, thank you for your reply. Unfortunately, I had tried that originally when I first ran into this problem. I tried losefocus on the field being tabbed out of and gainfocus on the field getting tabbed into and it doesn't change the behavior. It is as if the Tab key is always the last node in the chain of events no matter the type.

kazuyuki-mochizuki

Hi Edd,

Maybe something like this will work (not a very clean approach). Since you can assign value to the next field (ex edit 2). you can create a timer that watch for certain values for edit2. if it satisfies fire a forsmcript setfocus event to go back to edit1.

What I've tried is, I created a timer that runs every 3 seconds and calls the setfocus to edit1.

My UI sample

Form Script Code

Thanks,

Kazuyuki

Stephen Cena

Hmmmm... what about this... If you know that the event is going to the next field whether you like it or not, is it possible to set your TAB order such that it moves to a new 'dummy' fields which has a GainFocus event attached to it that in turn shifts the focus back to the component you want?

Copyright © 2025 Infor. All rights reserved.