Exclusive Notice On Opening mdb

[croy]

Access 2002 under Windows XP Pro with all patches.

On a split db with user-level security in place and working
well, the users in a custom, non-admin group always get a
message when the log on to the mdb:

"You don't have permission to open '[pathname]' for
exclusive use."

They all use a custom shortcut to open the db, and the
shortcut doesn't use the "/Excl" argument. Folks in that
group never want or need to open the db exclusively. Is
there an easy way to prevent that message?

 

[david]

Tools, options, open mode

(david)

 

[croy]

Tools, options, open mode

Thanks David.

On this Office 2002 box, there is
Tools|Options|Advanced|Default Open Mode.

That is set to "Shared".

Is that what you were referring to?

To the best of my understanding, that's the best way to set
it for the way we use the mdbs. But often-times, my
understanding lies somewhere between limited, and lunatic.

 

[david]

dunno then. Are you sharing the front end? That's not the normal
way to do it. I suppose that if you gave each user a copy of the
front end, they could all have 'exclusive use' permission.

Do you know if the message comes from the MDB or from the MDW?
When possible, I avoid problems by distributing copies of the MDW
as well as copies of the MDB.

Do you know if the message comes after you have started your
application, or before the application is loaded? Sometimes people
put stuff in the startup code that causes an attempt to shift to
exclusive use.

(david)

 

[croy]

dunno then. Are you sharing the front end? That's not the normal
way to do it. I suppose that if you gave each user a copy of the
front end, they could all have 'exclusive use' permission.

Not sharing the front-end. Each box has its own.

Do you know if the message comes from the MDB or from the MDW?
When possible, I avoid problems by distributing copies of the MDW
as well as copies of the MDB.

This notice comes up even when I'm at my box, logging into
the db with a lesser user's credentials. I had not noticed
this message in months past, just saw it within the last
month or so.

Do you know if the message comes after you have started your
application, or before the application is loaded? Sometimes people
put stuff in the startup code that causes an attempt to shift to
exclusive use.

Not sure where it's coming from, but there's no code in this
mdb that tries to force exclusing use.

 

[david]

Not sure where it's coming from, but there's no code in this

mdb that tries to force exclusing use.

That is, most commonly, code that tries to filter a form, but
it can be other things.

If you use the shortcut without the target MDB, so that
you log into the MDW and Access without the target
MDB, do you get the same message?

This problem happens when you are logged into Windows
as your self, but log into Access as someone else?

Since each user has their own copy of the front end,
there is no reason why they shouldn't have exclusive-open
permission on that mdb. Regardless of the reason, if that's
the problem, it's an easy fix.

(david)

dunno then. Are you sharing the front end? That's not the normal
way to do it. I suppose that if you gave each user a copy of the
front end, they could all have 'exclusive use' permission.

Not sharing the front-end. Each box has its own.

Do you know if the message comes from the MDB or from the MDW?
When possible, I avoid problems by distributing copies of the MDW
as well as copies of the MDB.

This notice comes up even when I'm at my box, logging into
the db with a lesser user's credentials. I had not noticed
this message in months past, just saw it within the last
month or so.

Do you know if the message comes after you have started your
application, or before the application is loaded? Sometimes people
put stuff in the startup code that causes an attempt to shift to
exclusive use.

Not sure where it's coming from, but there's no code in this
mdb that tries to force exclusing use.