General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
Title:
Opportunistic locking. Why disable on workstations?
Some time ago I read all I could about opportunistic locking. While there was plenty to read, I found none of it hung together to tell me how it works.
Now I'm looking to disable it. Looking at a few sources, there are instructions to disable it on a SERVER and separate instructions to disable it on workstations.
My question is this:
Considering my VFP application using native tables (most in DBCs) has all data stored/accessed/updated on the SERVER, why would I need to turn opportunistic locking off on the workstations???
Seems to me that if the server doesn't use OPLOCKS then any data sourced from it (and so under its control as far as buffer invalidations etc. is concerned) would be 'protected' from OPLOCK machinations. I don't particularly care about other data on the workstations.
cheers
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only