Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
"Could not save; currently locked by another user"
0 views
Skip to first unread message
TomM
Sep 29, 2008, 3:40:05 PM9/29/08
to
Here's the scenario:
An Access 2007 BE on a shared drive on a Netware server, with one table that
contains 3 records.
Client A, client B and client C all have a FE that links to that table.
If client A opens her FE first, client B can also open his FE.
If client B opens her FE first, client A can *not*open his FE (the message
"Could not save;..." appears).
An Access 2007 BE on a shared drive on a Netware server, with one table that
contains 3 records.
Client A, client B and client C all have a FE that links to that table.
If client A opens her FE first, client B can also open his FE.
If client B opens her FE first, client A can *not*open his FE (the message
"Could not save;..." appears).
any ideas?
TomM
Sep 29, 2008, 4:39:01 PM9/29/08
to
I should mention that this simple scenario was created to eliminate the
possibility that the problem is due to incorrect lock type on a ado recordset
or form.
possibility that the problem is due to incorrect lock type on a ado recordset
or form.
Joan Wild
Oct 1, 2008, 8:21:25 AM10/1/08
to
What permissions does client B have on the folder? All users need create
permission in order to create the associated ldb file. If B doesn't have
that permission, they can't create a ldb, and therefore open the mdb
exclusively.
permission in order to create the associated ldb file. If B doesn't have
that permission, they can't create a ldb, and therefore open the mdb
exclusively.
--
Joan Wild
Microsoft Access MVP
"TomM" <To...@discussions.microsoft.com> wrote in message
news:8AD066DF-93DD-4EF9...@microsoft.com...
0 new messages