Re-post 10/2 Request for Assistance

[The Maul Man]

Thank you, P. Do understand the what. Don't understand
the how. Reading many KnowledgeBase articles from search
on "exclusive," though no answer as yet.

All users are opening via desktop shortcut. No command
line "open exclusive." {Tools} {Options} are: Default
open mode - Shared, Default record locking - Edited
record, check True - Open databases using record-level
locking.

So I repeat the following post requesting assistance.

Thank you again

The Maul Man
----------------------------------------------------------
ORIGINAL REPLY TO POST OF 10/2/2003 . . . . . . . .
From: "Phobos" Sent: 10/2/2003 4:06:06 PM

The first person has the database opened exclusively.

P

----------------------------------------------------------
ORIGINAL POST OF 10/2/2003 . . . . . . . .

Subject: Re: placed in a state by user 'Admin'

in message . . .

Given: if one workstation has opened an .mdb (not split)
in design mode, a second workstation attempting to open
the database will receive a message such as ->
"Run-time error 3734: The database has been placed in a
state by user 'Admin' on machine ... that prevents it from
being opened or locked."

Question: under what other conditions would the same error
message be received by a second workstation attempting to
open a single .mdb?

We are intermittently being locked out by each other,
though first one in is a user using an application, not
someone doing design work, as is second one in, third one
in, etc. And second one gets the above error message
preventing it's opening the .mdb.

Is there possibly inherent either in Form or Report or VBA
functionality this consequence though one is not in
fact "doing design?"

Thanks for the help.

 

[Phobos]

When you use "File | Open..." instead of using the shortcut, you will see a
checkbox on the file open dialog with "Exclusive" next to it.

Make sure your merry men don't open the db with this checked.

P

 

[TheMaulMan]

Thanks again, P.

Application opens from shortcut with custom menu bar that
has no "File | Open". The users are locked into only what
the man behind the screen wishes them to see (a.k.a. Oz
Man.)

So for what else can I look?

 

[TheMaulMan]

Sorry, I probably should have said we are talking about
users who would have no clue how to fire up Access without
a shortcut. :-}

 

[Andy]

Make sure all users have read, write, delete permissions to the directory
the dB resides in. This allows the db to create a lock file (dbname.ldb). If
the lock file cannot be created, I believe the user is allowed access.
However, everyone else will be locked out.

I suggest you perform the development in a seperate directory, and I highly
recommend splitting your database.

hth,
Andy

 

[The Maul Man]

Thank you, Andy. Will check on the permissions (use
outside party to manage network.)

Development is performed in a separate directory and there
is only one developer (keeps coordination simpler, eh?)
That is why though I understand Design mode locking out I
haven't fathomed this locking out issue when none of the
users is in Design mode!!!

Do understand database splitting to be something to
attain. Are you also saying doing so has some bearing on
the locking out issue we are experiencing?

Thanks again for the help,

The Maul Man