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



>Tracy,
> I hope you don't mind but I wondered if you could give me your thoughts on an existing problem I have. One customer is complaining of slow performance. They have 15 concurrent users in my management program running on a Dell server with Novell 5. Boss man says he starts editing tickets and as he works through them the program keeps getting slower and slower. If he reboots the speed picks up but as he goes through more tickes it slows down again. My guess is it's not releasing the locks. They have a different company doing the network stuff for them. I talked to him and he said he did set extended file handles on. Any thoughts?
>
>Thanks again,
>John.
>
>>>
>>>>As far as Novell goes, here are troubleshooting tips for problems with workstations locking up connecting to Novell 4.x and 5.x servers, not achieving file locks, etc: