Database tries to open as exclusive even when default setting isshared

[microb0x]

Details about application:

Split front-end/back-end
both FE and BE reside on a NAS (network drive)
Single FE file that all users access (I know this is a bad idea but no
choice for the environment)

This is only happening with a single computer for this particular
front-end.

If the user double-clicks a shortcut I created on their desktop, which
is the same shortcut emailed to all the other users, they receive an
error about not having exclusive access.... etc.. Of course this is
while someone else has the front-end open, if no one has it open, it
opens fine just as exclusive.

If the user opens Access, then goes to File/Open and navigates to the
front-end and chooses the normal open open, not open read-only nor
either exclusive open, it works fine while others have the same front-
end open.

The users options are set to default open mode of shared.

Any idea why it is still trying to open as exclusive when using the
desktop shortcut?

 

[a a r o n . k e m p f]

Jet isn't reliable enough to be shared with multiple users.

move to SQL Server

 

[microb0x]

Jet isn't reliable enough to be shared with multiple users.

move to SQL Server









- Show quoted text -

While I appreciate both of your suggestions, even if Aaron is on his
typical rant, neither one really addresses my question... Why is it
trying to open as exclusive when it is set to shared?

I can have 15 (or more that is just an example) other user's all
accessing this single front-end with no issue, only this one computer
is having this issue. I will use Chris's suggestion of just giving
her another copy of the front-end for her use only, but this is a
short term fix until the real issue can be resolved.

Aaron, while I would prefer to use a SQL backend to a jet db, it's
just not an option here. There is no budget nor resource allocation
available for me to have a new db created on one of our many SQL
servers. Maybe in the future if this app gets enough use and
visibility within the company that would be an option, but for now I
have to live with the current setup. So I'd appreciate any assistance
with resolving this within my environment constraints.

 

[microb0x]

It just occured to me that the user has Adobe Acrobat Professional
installed. I seem to recall reading somewhere a while back that the
Adobe PDF Creator may be the cause of the issue. Does this sound
familiar to anyone?

If this is the case, does anyone know how to disable it for just MS
Access?

 

[microb0x]

It seems my memory served me correctly. The Adobe PDF toolbar is the
culprit. Here is thread of others with the exact scenerio I have and
the fix:

http://groups.google.com/group/micr...89?lnk=gst&q=exclusive+Adobe#aa5be82c7cedc789

 

[Larry Linson]

You may safely ignore Mr. Kempf's "standard advice for every question". Not
one poster has ever posted back to this newsgroup to thank him because his
"move to SQL Server" advice actually solved their problem.

Larry Linson
Microsoft Office Access MVP

 

[a a r o n . k e m p f]

good stuff

the funny thing is that Jet doesn't reliably work to 15 users, and
larry is giving a mis-diagnosis.
the funny thing is that Jet doesn't reliably work to 15 users, and
larry is giving a mis-diagnosis.
the funny thing is that Jet doesn't reliably work to 15 users, and
larry is giving a mis-diagnosis.

 

[a a r o n . k e m p f]

I'd reccomend upsizing, MS Access will generate an ADP for you.
and if you've got existing SQL Server, what does it cost money to make
another database on your existing servers lol?

 

[microb0x]

I'd reccomend upsizing, MS Access will generate an ADP for you.
and if you've got existing SQL Server, what does it cost money to make
another database on your existing servers lol?






- Show quoted text -

It's not a hard cost out of my pocket, but it does require hdd space.
Which the admins of the SQL servers are not going to allocate to me
without just cause.

With regards to your claim about reliability of 15 (or more) users
with a jet db, I have not had a single issue with regards to multiple
users. All of my non-adp access applications work just fine with many
users at the same time, and in a fews cases, a single front-end file
with many users. So long as you are diligent in your programming its
plenty reliable.

Again, this issue was related to a specific computer, and a conflict
with Adobe Acrobat injecting it's toolbar into Access, not because I
didnt use an adp.