ADE - file is locked for editing by anothr user...

[stuartb113 via AccessMonster.com]

Hi,
An ADE file that is accessed by multiple users returns the following msg when
accessed by more than one user:

The MS Access project will be opened read-only because one of the following
occurred:
The file is locked for editing by another user, or the file / folder is
marked as read-only

From previous posts i have tried starting up the ADE with the /ro startup
option in a dev environment by creating a one liner batch file as follows:

v:\dev\transfer\gbbadt\sparta.ade /ro

The issue now is only the first user to run the bat file, can open the ade
file...

I'd appreciate any assistance.

thanks
Stuart

 

[Vadim Rapp]

This happens when the file is indeed read-only or is opened by another user.
Microsoft recommends putting an individual ADE file on each workstation.

The message shows up only if the user has full Access. If it's Access
Runtime, there's no message.

There are, however, reasons to indeed set the ADE file as read-only and tell
the users with full Access to leave with the message.

Vadim


Hello stuartb113:
You wrote on Mon, 08 May 2006 13:25:09 GMT:

svA> Hi,
svA> An ADE file that is accessed by multiple users returns the following
svA> msg when accessed by more than one user:

svA> The MS Access project will be opened read-only because one of the
svA> following occurred:
svA> The file is locked for editing by another user, or the file / folder
svA> is marked as read-only

svA> From previous posts i have tried starting up the ADE with the /ro
svA> startup option in a dev environment by creating a one liner batch file
svA> as follows:

svA> v:\dev\transfer\gbbadt\sparta.ade /ro

svA> The issue now is only the first user to run the bat file, can open the
svA> ade file...

svA> I'd appreciate any assistance.

svA> thanks
svA> Stuart

svA> --
svA> Message posted via AccessMonster.com
svA>


With best regards, Vadim Rapp. E-mail: (e-mail address removed)

 

[Robert Morley]

That's a normal and expected error message when more than one person has the
file open. It will ONLY prevent you from making design changes to the ADE
(which is naturally impossible), I don't believe it will prevent you from
making data changes to the back end.

The ideal design here is to distribute the ADE and put a copy of it on each
of your users' machines. That will avoid this situation entirely.



Rob

 

[Vadim Rapp]

RM> making design changes to the ADE (which is naturally impossible),

Possible. The user can direct the connection to another database, for
example. Quite a change, isn't it.

Vadim

 

[Vadim Rapp]

VR> tell the users with full Access to leave with the message.

correction: tell them to LIVE with the message

 

[stuartb113 via AccessMonster.com]

I hadnt planned on distributing the ADE to each user.....is there not any
other solution??

That's a normal and expected error message when more than one person has the
file open. It will ONLY prevent you from making design changes to the ADE
(which is naturally impossible), I don't believe it will prevent you from
making data changes to the back end.

The ideal design here is to distribute the ADE and put a copy of it on each
of your users' machines. That will avoid this situation entirely.

Rob

Hi,
An ADE file that is accessed by multiple users returns the following msg

[quoted text clipped - 19 lines]

thanks
Stuart

 

[Robert Morley]

Interesting...I've never actually used ADE's to this point, so sort of
assumed they were the same as MDE's. Thanks for the head's up.


Rob

 

[Robert Morley]

As Vadim said, tell them to live with the error message (and trust that they
won't make changes to the connection on you!).



Rob

 

[Vadim Rapp]

Hello stuartb113:
You wrote on Mon, 08 May 2006 15:15:50 GMT:

svA> I hadnt planned on distributing the ADE to each user.....is there not
svA> any other solution??

Uninstall their Access and install Access Runtime. From the
management/security point of view, it's step in right direction: users won't
be able to create a query that by coincidence will exploit a security
vulnarability you overlooked, and they won't have a tool to develop their
own report based on columns abandoned 5 years ago. Of course I don't know
your environment, so it's kinda blind shot.

Vadim