Hi Lev,

I just went back to your original message.

Perhaps you should consider getting rid of the forms set and use a form manager instead. This is what most frameworks rely on in order to have the functionality you're seeking.

Alex


>Dear Alex:
>
>Thanks for your suggestion. Unfortunately, I must use a modeless child form, because the parent form contains navigation controls. Therefore, the parent must be available to go to the next or previous account, and then send a command to the child form to refresh itself based on this new account.
>
>The program is almost consistently crashing upon the second entry, and only when I close the child form (which then sets the flag and causes the parent to close). So I run the form(s), close the child form (which closes the parent), then run the form again, and before anything is displayed FoxPro crashes.
>
>Lev