MB> LEE ARONER wrote in a message to GEORGE FLIGER:
 LA>    You would only see it if locking calls were being made
 LA> from the     clients, across the wire. If your DBMS runs on
 LA> the server and all     locks are placed from the server, you
 LA> won't see any affect.     
MB> Also, however, you will not see problems if you are running software such 
as
  > Microsoft Access or Borland/Corel Paradox that expects oportunistic 
locking.
   Actually, I know of at least one instance of an Access DB that 
   was experiencing corruption. In that case, turning off OpLocks 
   cured the problem, but resulted in a significant decrease in 
   apparent bandwidth.
   The problem really has nothing to do with whether the application 
   is "expecting" op locks, it's just plain buggy code by Novell.
                                       LRA
 -- SPEED 2.00 #2720: What if there were no hypothetical situations?
--- Platinum Xpress/Win/Wildcat5! v2.0
---------------