I forgot to mention..You are totally correct in that if the focus is given to one of a few objects on the 1st modal form after the 2nd modal form returns, there is no c5. I did this a few different ways, a WAIT WINDOW actually any time between the button click that brings up the 2nd modal form(even if that WAIT WINDOW comes in the 2nd modal form's code) will totally prevent the error..I figure this WAIT WINDOW is doing something with focus, perhaps giving it to the object who calls it..I say that because if I put a WW in the destroy() method of one of the objects that can have focus when you bring up the 2nd modal window to cause the error, I will *always* get the error no matter what widget has focus when the 2nd modal form exits the way I mentioned.

The c5 isn't my real problem here..cause we've got a workaround, but I'm trying to apply what I've learned with it to some other, much more prevalent c5's we're getting as we suspect focus/form creation-destruction as a cause of those...

But thanks for the input, I'll try what you suggest.