Access 2007 with a 2003 mde and Error 3734

[Susan Denniston]

Hello - hoping someone can help.

We have an Access 2003 mdb (back-end) with a companion Access 2003 front-end
which we distribute as an .mde.

The 2 databases reside in a shared folder on the server--we do not
distribute the mde to every workstation. This has worked well for us and we
are hoping not to have to distribute the mde to the workstation level.

We are upgrading from Office 2003 to Office 2007. We intend to continue
using the 2003 databases via Access 2007 (the application will be retired in
the near-term - no desire/need to upgrade to accdb)

Using Access2007, we open the front-end mdb, and make a new mde.

From Access 2007, User 1 opens the mde just fine. When user 2 attempts to
open it, they get the infamous Error 3734 "db has been placed in a state etc
etc that prevents it from being opened."

Oddly, when opening the front-end .mdb, the locking does not occur--a 2nd
user gets in just fine.

We are contemplating whether we might have to distribute the .mdb front-end
instead, employing other techniqes to protect it from design changes. But we
would rather really understand and correct what's happening with the mde.

Thanks in advance,
Susan Denniton

 

[Marco Pagliero]

From Access 2007, User 1 opens the mde just fine.  When user 2 attemptsto
open it, they get the infamous Error 3734 "db has been placed in a state etc
etc that prevents it from being opened."
Oddly, when opening the front-end .mdb, the locking does not occur--a 2nd
user gets in just fine.

When user 1 opens the mde, you go to Tools / Options / Advanced
What is the setting of Default Open Mode: Shared or exclusive?

We are contemplating whether we might have to distribute the .mdb front-end
instead, employing other techniqes to protect it from design changes.  But we
would rather really understand and correct what's happening with the mde.

You could distribute the mde, I think.

 

[Susan Denniston]

Hi Marco - thanks for your reply.
The Default Open Mode = Shared, and the Default Record Locking = No Locks.

If we can't track down the root cause, then we will either distribute the
..mde to the workstation level, or lock-down the .mdb in a different way and
distribute that to the server level.

Thanks,
Susan