B
B Hope
We have an XP Home machine on a peer network with a normal database .mdb
file. Immediately the folder containing the database is shared, everyone on
the network can see the database and use it. However, the database is
occasionally opened in exclusive mode and then closed again but after this
has happened the other users can no longer open the database. They get the
following message:
"The Microsoft Jet database engine cannot open the file \path\xyz.mdb. It
is already opened exclusively by another user, or you need permission to
view its data".
We would expect the other users to see such a message in exclusive mode but
not once the database has closed.
The really strange thing we have found is that if the folder share is
removed and re-applied, the other machines can access the database again.
I am not aware that the machine is using NTFS (and I will check this out
next week) but what could be the reason for this sharing problem and why
does re-setting the share seem to fix it? There are no special permission
options like in XP Professional, so is XP Home doing something that we are
unaware of?
Yours hopefully
Barry
file. Immediately the folder containing the database is shared, everyone on
the network can see the database and use it. However, the database is
occasionally opened in exclusive mode and then closed again but after this
has happened the other users can no longer open the database. They get the
following message:
"The Microsoft Jet database engine cannot open the file \path\xyz.mdb. It
is already opened exclusively by another user, or you need permission to
view its data".
We would expect the other users to see such a message in exclusive mode but
not once the database has closed.
The really strange thing we have found is that if the folder share is
removed and re-applied, the other machines can access the database again.
I am not aware that the machine is using NTFS (and I will check this out
next week) but what could be the reason for this sharing problem and why
does re-setting the share seem to fix it? There are no special permission
options like in XP Professional, so is XP Home doing something that we are
unaware of?
Yours hopefully
Barry