Hello
We've been having a problem with DBF databases running on a Windows 2003 Server in a workgroup environment. The (XP) client machines run Clipper 5.2 programs, often doing massive amounts of reads on large .DBF files - when only one client is doing this it runs very fast, taking circa 15 seconds to finish. However if another client also tries to run the search after this it will run incredibly slowly and take 3 to 4 minutes. The databases themselves are still showing as being open files in Computer Management for a while after the client's search is complete - and when they are released the search will run as speedily as before. (The speed of the search if it's run from the server never changes and takes about 15 seconds.)
We have tried various solutions found on the web:
-disabling Opportunistic Locking and Caching in the registry only made every search slower
-disabling "digitally sign communications" didn't apply because we are in a workgroup not domain
Please help!
We've been having a problem with DBF databases running on a Windows 2003 Server in a workgroup environment. The (XP) client machines run Clipper 5.2 programs, often doing massive amounts of reads on large .DBF files - when only one client is doing this it runs very fast, taking circa 15 seconds to finish. However if another client also tries to run the search after this it will run incredibly slowly and take 3 to 4 minutes. The databases themselves are still showing as being open files in Computer Management for a while after the client's search is complete - and when they are released the search will run as speedily as before. (The speed of the search if it's run from the server never changes and takes about 15 seconds.)
We have tried various solutions found on the web:
-disabling Opportunistic Locking and Caching in the registry only made every search slower
-disabling "digitally sign communications" didn't apply because we are in a workgroup not domain
Please help!
