K
Keith
The database has been placed in a state by user 'admin' on machine 'BHD020'
that prevents it from being opened or locked.
I have 20 pcs each running a different copy of an excel sheet that does a
Microsoft Query refresh once every 15 minutes. They do this 7 days per week
and 24 hours per day. Occasionaly we would receive this error and have to
manualy click "Cancel" or "OK". If you select OK it then does an ODBC login.
Recently this is failing much more often.
We are using office 2003, in Windows XP. The access database is located on a
network server. There is no pattern to the error. It happens all times of the
day and night.
Is this because two pcs are performing an ODBC login at the same time? Can I
solve the error by changing the way they log in? For example: Is it possible
to change them all to read only? Would this let multiple pcs in at the same
time without conflicting with each other.
None of them need to write to the Access database.
that prevents it from being opened or locked.
I have 20 pcs each running a different copy of an excel sheet that does a
Microsoft Query refresh once every 15 minutes. They do this 7 days per week
and 24 hours per day. Occasionaly we would receive this error and have to
manualy click "Cancel" or "OK". If you select OK it then does an ODBC login.
Recently this is failing much more often.
We are using office 2003, in Windows XP. The access database is located on a
network server. There is no pattern to the error. It happens all times of the
day and night.
Is this because two pcs are performing an ODBC login at the same time? Can I
solve the error by changing the way they log in? For example: Is it possible
to change them all to read only? Would this let multiple pcs in at the same
time without conflicting with each other.
None of them need to write to the Access database.