>Two things...first of all, do you really need to add chighlighteffect (in addition to cmouseoverfx)? By default, cmouseoverfx instantiates its own copy of chighlighteffect...it's the default effect. You should be able to just drop an instance of chighlighteffect on the form and call its SetEffect() and CancelEffect() methods.

I didn't realise this. I took off the chighlighteffect control, but the login form still stays in memory.

>Secondly, I recommend trying this on the Framework's sample application...see if you get the same result.

Yes. The same result in projmgr6 with the cmouseoverfx control dropped on the loginform. Without it, the loginform is not in memory. All I do is drop on the mouseoverfx, set the buttons to use it in their mousemove(), set the form mousemove() to cancel the effect, run the app, logon and then suspend and do a display memory.

In our application, we have a form for adding new customers called patientchart. As we add new customer and the exit the chart, it also stays in memory. All our forms have the mouseoverfx control. One strange thing I noticed is that after calling the form a few times, the numbers in the display memory dump are the same. The FROM and TO numbers are identical as are the total bytes. Is that normal? Is that eating resources?