>>I had to ask again, because your WEXIST does not make sense in case of modeless form, because DOform will not stop execution, it will continue further so WEXIST will always return true.
>>Now let me ask you another question to make sure: do you want changes to appear in Search form immediately when something is done in Ticket form, or after Ticket form is closed?
>
>I think I want them after the Ticket form is closed, though immediate change may be even better.
>
>BTW, don't forget that it's multi-user, so other users may change other tickets at the same time...

Whatever the option, the application flow would be following. Firstly, your ticket form should keep a reference (property) to the search form. Most likely you can pass the value when you start ticket form (assuming it's always done from the search form). Now whenever you make critical change or from ticket form Destroy event (if you want changes on close point) you may call specific method (my favorite name is 'OutsideCall') of the search form with appropriate parameter (mode). The OutsideCall method will make all necessary manipulation within the search form, i.e. in general, OutsideCall method contains DO CASE triggering different code depending on the passed parameter.