>Hi Harry,
>
>The situation I encountered when I had to insert the timing loop involved activating a form that wasn't topmost. The problem was that the form had to be completely on top. The code that activated the form wouldn't produce the correct results if it weren't. Remember that VFP, tells the system to do this and goes on its merry way, regardless of whether or not the action has been completed.


yeah, tell me about it! (See my latest post on event processing...)


>
>I found something similiar with WEXIST() still returning .T. in the debugger even after the form had been released. When I minimized, then restored it, the debugger showed .F.
>
>Here's an idea if you're using VFP 6.0. If you wrap the form object in another object, say a Session, and create an object reference as a custom property of it, you can add an _Assign event for the form object. _Assign will fire whenever the object reference is assigned. When the form is released, the parameter coming into the event will be .NULL., you can then use this as an indicator to do you're cleanup chores. You don't have to fool around with WEXIST() and have to worry about timing problems either.
>

I think I almost understood that! :)

Harry