[Migrated content. Thread originally posted on 22 July 2010]We have a couple of screens where we use the Msg-Validate EVENT on an entry field. The screen also has a button that the user can click to 'save' the information.
In the validate event we check for valid data (I assume this is what it is for), and if the data is invalid then we give the user a message and do the following to keep the cursor in the field.
SET EVENT-ACTION TO EVENT-ACTION-CONTINUE.
Now the problem arises under thin client when the network is slightly slower than normal (it appears this is when it happens most anyhow). The user may have entered invalid data but instead of tabbing out of the field, they click on the save button and what seems to happen is the cmd-clicked event fires BEFORE the Msg-Validate EVENT and a mess of problems arise.
Has anyone come across this before or have any idea how to circumvent or better handle this situation?