We have a client who is getting serious slowdown when running our application and making edits to the tables.  The problem occurs whether
they connect using the client/server engine or as a fileserver.  This problem has been seen on two different physical servers, one running
Server 2000, the other Server 2003 (both are enterprise editions).  The strange thing is that when we tried using a copy of their database on
our site, we had the same problem at first, but after deleting their copy of the dbisam.lck file (which was copied along with their data) the
slowdown disappeared.  Having them do the same thing on their server does not make a difference, however.

Are there any known issues with how various versions of Windows create and/or edit this file?  What could possibly cause this to happen?

Robert,

<< We have a client who is getting serious slowdown when running our
application and making edits to the tables.  The problem occurs whether
they connect using the client/server engine or as a fileserver.  This
problem has been seen on two different physical servers, one running Server
2000, the other Server 2003 (both are enterprise editions).  The strange
thing is that when we tried using a copy of their database on our site, we
had the same problem at first, but after deleting their copy of the
dbisam.lck file (which was copied along with their data) the slowdown
disappeared.  Having them do the same thing on their server does not make a
difference, however.

Are there any known issues with how various versions of Windows create
and/or edit this file?  What could possibly cause this to happen? >>

Not that I'm aware of.  The .lck is normally very small and is only
read/edited in very specific circumstances during table creations or
database opens.  The rest of the time it is used for locking calls only.

--
Tim Young
Elevate Software
www.elevatesoft.com