A
Andrew Wiseman
I have set up a simple (unsplit) Access 2000 database with a single table
whose records are editable in a form. I observe the following behaviour when
two instances of Access 2003 are attempting to use the same database (that
is whether two users are accessing the MDB file from a network share or the
application and *.MDB file is on a local machine with a single user running
two instances of Access)...
1. If two instances are running and a record is edited (using the form) in
one of the instances, when the user attempts to save the change, he gets the
message: "Microsoft Access can't save design changes or save to anew
database object because another user has the file open. To save your design
changes or save to a new object, you must have exclusive access to the
file." This happens even if the two instances are pointing at different
records.
2. If only one instance is running, a user is able to save changes to a
record in the form. But having done so, attempting to run a second instance
of the database fails, with the message: "The database has been placed in a
state by user 'Admin' on machine 'XXX' that prevents it from being opened or
locked."
If I look in Tools Options Advanced in MS Access, I see the default open
mode is shared, the default record locking is set to "No locks" and the
"Open databases using record-level locking" is ticked.
I seem to be having exactly the same problem as the guy in this forum
describes:
http://www.duxcw.com/yabbse/index.php?board=10;action=display;threadid=15035
Anyone know the quickest way of solving this problem? (I'm looking for a
lazy option that doesn't involve splitting databases, compiling front ends
or adding user accounts and security!)
whose records are editable in a form. I observe the following behaviour when
two instances of Access 2003 are attempting to use the same database (that
is whether two users are accessing the MDB file from a network share or the
application and *.MDB file is on a local machine with a single user running
two instances of Access)...
1. If two instances are running and a record is edited (using the form) in
one of the instances, when the user attempts to save the change, he gets the
message: "Microsoft Access can't save design changes or save to anew
database object because another user has the file open. To save your design
changes or save to a new object, you must have exclusive access to the
file." This happens even if the two instances are pointing at different
records.
2. If only one instance is running, a user is able to save changes to a
record in the form. But having done so, attempting to run a second instance
of the database fails, with the message: "The database has been placed in a
state by user 'Admin' on machine 'XXX' that prevents it from being opened or
locked."
If I look in Tools Options Advanced in MS Access, I see the default open
mode is shared, the default record locking is set to "No locks" and the
"Open databases using record-level locking" is ticked.
I seem to be having exactly the same problem as the guy in this forum
describes:
http://www.duxcw.com/yabbse/index.php?board=10;action=display;threadid=15035
Anyone know the quickest way of solving this problem? (I'm looking for a
lazy option that doesn't involve splitting databases, compiling front ends
or adding user accounts and security!)