G
Gail
I designed a database that is located on the shared drive
of a network server. We have been using this db for about
4 months with no problems. However, this week, we started
to see numerous errors whenever someone tries to open the
database when someone else has been using if for a period
of time. This is what happens:
Person A is already using the db.
Person B tries to open the db and gets this message:
The database 'S:\....' needs to be repaired or
isn't a database file.
You or another user may have unexpectedly quit
Microsoft Access while a Microsoft Access database was
open. Do you want Microsoft Access to attempt to repair
the database?
When Person B clicks yes, he will get this message:
You attempted to open a database that is already
opened exclusively by user "Admin' on machine '....'. Try
again when the database is available.
Once the yes button is clicked a msg appears that says
it can't be repaired or isn't adatabase.
However, once Person A closes the database, Person B will
get the same message as before, but will be able to repair
the database.
Do you have any idea as to why we get this message.
Someone mentioned that it might have to do with where it
is on the server. However, it is just in a folder on the
shared drive. Could it be the size of the file? It's
about 73,472KB.
Occasionally, we have had situations where Person B will
get a message that the file is opened exclusively on their
own computer... even after they shut it dowm completely.
We have found that the only way to get around that is to
delete the lock file (Access.LockFile.9).
Any help you can provide is certainly appreciated.
of a network server. We have been using this db for about
4 months with no problems. However, this week, we started
to see numerous errors whenever someone tries to open the
database when someone else has been using if for a period
of time. This is what happens:
Person A is already using the db.
Person B tries to open the db and gets this message:
The database 'S:\....' needs to be repaired or
isn't a database file.
You or another user may have unexpectedly quit
Microsoft Access while a Microsoft Access database was
open. Do you want Microsoft Access to attempt to repair
the database?
When Person B clicks yes, he will get this message:
You attempted to open a database that is already
opened exclusively by user "Admin' on machine '....'. Try
again when the database is available.
Once the yes button is clicked a msg appears that says
it can't be repaired or isn't adatabase.
However, once Person A closes the database, Person B will
get the same message as before, but will be able to repair
the database.
Do you have any idea as to why we get this message.
Someone mentioned that it might have to do with where it
is on the server. However, it is just in a folder on the
shared drive. Could it be the size of the file? It's
about 73,472KB.
Occasionally, we have had situations where Person B will
get a message that the file is opened exclusively on their
own computer... even after they shut it dowm completely.
We have found that the only way to get around that is to
delete the lock file (Access.LockFile.9).
Any help you can provide is certainly appreciated.