>We've run into this problem as well, and found a simple workaround that seems to work. It involves setting the form's Visible property to .f. at the beginning of the form's Destroy event (before running the framework's default code). For some reason, this seems to keep the form controls from trying to access their control sources (after their source data has been destroyed).
>
>Hope this helps......Eddie

Eddie,

This should work in my case too. What's happening (I guess) during the destroy is some flicker that makes the form appear again and the SetFocusToFirst() to fire.

José