Randy,

> I put a suspend() in the cmouseoverfx.cleanup(). When I ran my app, it did not suspend when I closed the login form. The cleanup() did get called when I exited the application. The same thing happened when I put code in login.Destroy(). It didn't execute when the form closed, only when I exited the app. I don't understand why this is happening, but it's causing us some problems with our high volume customers running out of resources.
>Thanks for your help.

I guess, the mouseoverfx should be destroyed, before all the other controls are destroyed.

The last control that appears in the property sheet's control combo box is the first that is being destroyed, when the form releases. If mouseoverfx isn't the last control in the list, select the mouseoverfx control on the form class and do a "Bring to front". The change won't be visible immediately. You will have to close the class designer and open the class again to see the change.

HTH,
Armin