>Hi Chris
>
>>Are you calling the login form manually, or letting the framework start it for you?
>
>Standard framework stuff.
>
>When you use DoForm with a modal form like the login form, the default behavior is to hide the form, not destroy it. This is to let DoForm continue executing and process any returned value. Try moving your suspend to the loginform.hide().
>
>We use cbizobjmodalform for most of our forms because we need the return value. It seems that the cmouseoverfx control is interfering with the release of the form. If I'm understanding the code properly, when loObject goes out of scope in the utility.prg after uretval has been returned, the form should get destroyed. Is that the way you see it?

Yes. Although I haven't used the cmouseoverfx myself, it does sound like there's still a dangling reference that is keeping it alive. I was suggesting the .hide() as the next place to start looking at it.

Did you perhaps override the Destroy method of the form and cmouseoverfx without a dodefault (or explicit call to cmouseoverfx.cleanup()) to release the object references?