On 3 Jan 98 11:41pm, LEE ARONER wrote to GEORGE FLIGER:
 LA>    AFAIK, the latest version of Client32 still defaults to "ON"
 LA>    for Packet Burst and Opportunistic Locking, which will
 LA>    destroy server files of any application (mostly databases)
 LA>    that make DOS file locking calls across the wire.
GF> If those options are a problem for you you can always adjust them to
  > suit your needs and even turn them off, however, I've not had these
  > server file problems you describe with our inhouse server-based
  > databases.  It sounds to me like you have more of a SHARing problem.
  > Are you utilizing share properly with the appropriate files and locks
  > defined for your database?  Have you attempted to flag all you database
  > files (only the DBs, not the indexes) for Transactional Tracking?
 LA>    The problem is well documented and acknowledged by Novell.
 LA>    They just haven't done anything about it.
GF> I must live a charmed database life.  I've not been subject to these
  > issues.
 LA>    You would only see it if locking calls were being made from
 LA>    the clients, across the wire. If your DBMS runs on the
 LA>    server and all locks are placed from the server, you won't
 LA>    see any affect.
Aha!  That explains it then.
George
... A lover teaches a wife all that her husband has concealed from her.
--- Via Silver Xpress V4.4P [Reg]
---------------