Hi again Marcus,

We found the problem, but have not found a solution. The reason our forms are not releasing is because we are using the cmouseoverfx and the chighlighteffect controls from the ceffects library, dropped on the logon form. This is causing all our forms to stay in memory.

Now for the hard question. How to fix it. I deleted the controls from the form and then used addobject() in the init of the form to see if that would release it, but it didn't. I've tried putting a chighlighteffect.release() in the form.destroy(). That doesn't do it either.

Any suggestions?



>Hallo Randy,
>
>>Can anyone tell me if they are seeing this behavior with their MM app. After I login, the login form is still showing up with display memory also.
>>
>>What would cause the login form not to release from memory?
>I already tried to get your behavior this morning, but I wasnt able to
>reproduce it so i kept quiet <g>
>
>If you dont get any other answer, I would try to debug the destroy event of the login form and try to figure out why it is not destroyed.
>
>If you dont run through this try to set a breakpoint in Function DoForm in Utilities.prg. After showwing the Loginform it should be destroyed, which should run LoginForm.Destroy() Event.
>
>If everything seems to run fine but the form is stil there you normally have any kind of dangling reference to the form wich prevents it from really beeing removed. Perhaps you can find out if you do anything in the form that is not MM standard.
>
>When nothing else helps, try to check out if you have the same behavior in the projects manager example.
>
>Marcus