>Has anyone noticed that there is no way of totally freeing up memory after instantiating a class then removing it? I have a system which receives data over a telephone network. In a "good" day I may receive over 10000 events. In the 'old' days (FP2.x) I would use numerous memvars and save events to files. Now I instantiate an object and populate properties of the object before storing interpreted results. Problem is every time I CREATEOBJECT() or AddObject() I loose memory according to SYS(1016). Soon my app slows to a crawl. I am, BTW removing the object RemoveObject() or releasing the reference to it.
>
>The only way I have been able to get around this is to create the needed objects at the outset of the app and simply reuse them every time I get a new message.
>
>Is this correct? Even from the command window if you CREATEOBJECT() and then release the reference, you can see memory creeping away. The only way to get it back is with a CLEAR ALL.
>
>Any thoughts?
>
>Rick Grinter
Have you tried RELEASE MyClassInstance?
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer