J
James Palmer
Guest
If you're on a modern Progress version then Client Request Statement Cache is probably what you need: knowledgebase.progress.com/.../P150383 Be careful with it - best to turn it on just for certain users and turn it off again as there are some bugs in some versions. A share lock often occurs when the code itself doesn't specify a lock. Run development and test with the -NL option which forces a no-lock. If there are places that don't have a specific lock specified then you'l know about them soon enough! Once you're happy you've ironed out all those issues you can run Production with -NL too.
Continue reading...
Continue reading...