User placed database in a state...

[Richard Choate]

When my client opens her Access 2K db, the second user who opens it AND THEN
opens one of the forms, will get the error:

The database has been placed in a state by user <whomever> on machine <name>
that prevents it from being opened or locked. Error 3734. (explanation: this
error occurs when the new passive shutdown/connection control is being used.
This error message indicates that a user set the database in a mode that
will prevent other uses from opening it.)

They do not have it set to open exclusive by default. What do you think
could be happening?

Richard Choate

 

[Hugh O'Neill]

When my client opens her Access 2K db, the second user who opens it
AND THEN opens one of the forms, will get the error:

The database has been placed in a state by user <whomever> on machine
<name> that prevents it from being opened or locked. Error 3734.
(explanation: this error occurs when the new passive
shutdown/connection control is being used. This error message
indicates that a user set the database in a mode that will prevent
other uses from opening it.)

They do not have it set to open exclusive by default. What do you
think could be happening?

Richard Choate

As this is a multi-user database system, have you split the database
into font and back ends with a copy of the front end on each user's PC?

Hugh

 

[Richard Choate]

Actually, although these people are a client, I did not build their database
nor do I manage it for them. I can tell you though, that this database is
not split and should not be. There are only 3 users and about 4K records at
most in their largest table. Usually it is only one user but there could be
two or three on some days. Jet can handle this fine.

After posting this, I found a couple of items in the KB that are probably on
point. She is using Access2K, she has a form with a subform, the main form
has a control which refers to the subform, and the problem doesn't occur
unless one of them has the form open. There was a bug in Access 2K which was
fixed in Service Release 1, which accounts for this error. I advised my
client of this and they have not had a chance to install the service pack
yet to test it and see if it worked. I think this is a solution, though.

I'm still interested in your thought, however. Do you have an idea?

Thanks,
Richard Choate

When my client opens her Access 2K db, the second user who opens it
AND THEN opens one of the forms, will get the error:

The database has been placed in a state by user <whomever> on machine
<name> that prevents it from being opened or locked. Error 3734.
(explanation: this error occurs when the new passive
shutdown/connection control is being used. This error message
indicates that a user set the database in a mode that will prevent
other uses from opening it.)

They do not have it set to open exclusive by default. What do you
think could be happening?

Richard Choate

As this is a multi-user database system, have you split the database
into font and back ends with a copy of the front end on each user's PC?

Hugh

 

[Hugh O'Neill]

Actually, although these people are a client, I did not build their
database nor do I manage it for them. I can tell you though, that
this database is not split and should not be. There are only 3 users
and about 4K records at most in their largest table. Usually it is
only one user but there could be two or three on some days. Jet can
handle this fine.

After posting this, I found a couple of items in the KB that are
probably on point. She is using Access2K, she has a form with a
subform, the main form has a control which refers to the subform, and
the problem doesn't occur unless one of them has the form open. There
was a bug in Access 2K which was fixed in Service Release 1, which
accounts for this error. I advised my client of this and they have
not had a chance to install the service pack yet to test it and see
if it worked. I think this is a solution, though.

I'm still interested in your thought, however. Do you have an idea?

Thanks,
Richard Choate




As this is a multi-user database system, have you split the database
into font and back ends with a copy of the front end on each user's
PC?

Hugh

You may well have hit on one reason for the malfunction. However, any
multi-user Access database should be split (using the built-in tool) so
that the shared data Tables reside on the server and a copy of the
front end is run on each separate PC terminal.

hth

Hugh