We have a timeclock application shared out on our network. The backend is a 2002/2003 .mdb file stored on our file server with very liberal permissions set on the share.
If more than one user has a bound form open then bound forms take 5 to 15 seconds to open for all users. Also, if one user has a bound form open then my DAO-code-driven unbound form on the main punch clock also takes anywhere from 5 to 15 seconds to complete a data operation.
Running compact and repair on the backend and all the frontends doesn't fix the problem.
When I run process monitor on my computer while waiting for a form to open, I see varying quantities of the following entries:
Process Name - Operation - Path - Result
MSACCESS.EXE - LockFile - S:\TimeClock\TimeClock_BE.ldb - FASI IO DISALLOWED
MSACCESS.EXE - LockFile - S:\TimeClock\TimeClock_BE.ldb - NOT GRANTED
MSACCESS.EXE - CreateFile - S:\TimeClock\TimeClock_BE.ldb - SHARING VIOLATION
Any Suggestions on where to look and how to troubleshoot this issue?
If more than one user has a bound form open then bound forms take 5 to 15 seconds to open for all users. Also, if one user has a bound form open then my DAO-code-driven unbound form on the main punch clock also takes anywhere from 5 to 15 seconds to complete a data operation.
Running compact and repair on the backend and all the frontends doesn't fix the problem.
When I run process monitor on my computer while waiting for a form to open, I see varying quantities of the following entries:
Process Name - Operation - Path - Result
MSACCESS.EXE - LockFile - S:\TimeClock\TimeClock_BE.ldb - FASI IO DISALLOWED
MSACCESS.EXE - LockFile - S:\TimeClock\TimeClock_BE.ldb - NOT GRANTED
MSACCESS.EXE - CreateFile - S:\TimeClock\TimeClock_BE.ldb - SHARING VIOLATION
Any Suggestions on where to look and how to troubleshoot this issue?