Try moving the code to the CanDepart event. Then issue a doDefault if 
the code passes or a "... Errormessage ... setErrorCode(CanNotDepart) 
... Exit()" if the code fails. So there shouldn't be a difference in 
tabbing or clicking a button.

On 23/04/2023 2:12 pm, Ivan Kuhle wrote:
> Just wondering if someone can help with a bothersome issue that occurs on
> an old Paradox application:
> I have a form with a bunch of undefined fields. On data entry, a
> changeValue event fires when tabbing to another field. However, if a
> user selects a button such as close etc., then changeValue doesn't
> fire, and the data doesn't write to the table. I'm sure there's a
> simple solution, but I can't remember...
> Any pointers will be appreciated.
> The buttons are set to tab stop. Using Paradox 10 on Windows 10.
> (Sorry if this is the wrong group.)