Jim,
your advice is very welcome. We do a ton of VFP SQL suff working in the tickets. Could be as many as 10 or more of them for the work in one ticket as we call other procedures any number of times. ie. One ticket can have multiple POs and each PO can have multiple invoices. We are pretty good about closing files as we come out of each session but we will definatly take a closer look. What you are saying about SQL does jive with the problems. As for objects, we are only opening normal screens with nothing fancy at all.

Thanks a million,
John.



>John,
>
>Obviously, I'm not Tracy.
>
>But this doesn't sound like a lock type of problem given that you only report a slow-down (that is, no messages or other stuff).
>It *does* sound like you may have some kind of memory 'leak' - possibly some object NOT getting released between ticket edits. Keep in mind that a RELEASE command will do nothing on an abject *if* there is still some reference in some memvar somewhere to that object. Processing will merrily continue along BUT the object in question will stay in RAM. If you are creating some object(s) with every ticket it could be them that are building up in RAM, eventually forcing use of SWAP space with a concomitant slowdown.
>Another case I remember seeing reported here is that numerous consecutive SQL commands can, under certain circumstances, chew up RAM. In that case the 'solution' was to be sure to close all of the tables involved periodically.
>
>good luck