Larry,

This long-distance 'debugging' with little real info is guesswork at best...

I will assume that the second instance is from a stop of the application followed by a restarting of it by the user.

There are possibly 2 different problems here:
1) slowly increasing RAM usage;
2) improper shutdown of the application (internally, not by the user).
The first can cause the second, I think, in some cases.

The slowly increasing RAM is most likely caused by non-releasing of some object, though things like repeated USE...AGAIN (or just USE...?) without CLOSE or USE IN... may cause it.
Non-releasing of an object can easily occur if you have a "dangling reference" hanging about. A "dangling reference" occurs when you keep a REFERENCE to some object or object property in some memvar and do not NULL or release that memvar before releasing the object itself (the one that is related to the memvar in question). A RELEASE of that object will do nothing, though it will NOT report an error either.
So if there are places in any of the executing code where you do something like...

memvar1 = SomeObject.Company

...then command

RELEASE SomeObject

will do NOTHING unless you have previously done either

STORE .NULL. TO m.memvar1

or

RELEASE m.memvar1

I hope this helps, and good luck


>Jim -
>I just got an email from the user which reads as follows:
>" There are two instances running only one is really active. The one that is active is steadily increasing in the amount of memory it is using..."
>
>The app. is an exe, how to if refresh or cash out the memory or manage my instances?
>Would this help or am I barking up the wrong tree?
>
>Larry