To All,



Same question as posted 8/15/01. No significant takers on the question. 

Let me rephrase, and perhaps reiterate...



Access DB sitting in a Novell server. 5 of us have admin rights to the 

program. The rest of the users have only read-write access. I thought 

that I would be able to work on objects within the DB provided no other 

person was working with that object. I found I cannot access any design 

changes or maintenance if ANYONE AT ALL is in the program.



Doesn't Access employ object level locking somehow? If so, where do I 

find it, and how do I go about employing it so that I don't have to 

"chase the whole user list out" before I can maintain anything????



Thanks for any light anyone can shed on this.



Regards,



Tom

The answer is no--ever since A2K, Access wants an exclusive lock on the

entire .mdb file in order to save design changes.  See



http://support.microsoft.com/support/kb/articles/Q200/2/90.ASP



for more details.



The solution is to split your app into front (queries, forms, reports,

modules, etc.) and back (tables) ends.  Each user gets her own copy of the

front-end, but they all share the back-end.  That way you only have to chase

them out if you need to work on the back-end, which is normally rare.  Go to

Tools -> Database Utilities -> Database Splitter for an automated method of

splitting your db.  There are some nice side effects of doing so (local temp

tables w/no worries of user collisions, modest performance increase from

having some objects stored locally).



Cheers,



-Roy



-----Original Message-----

From: Thomas A. Benjock [mailto:TomBenjock@w...]

Sent: Thursday, August 16, 2001 12:25 PM

To: Access

Subject: [access] Access Object Level Locking?





To All,



Same question as posted 8/15/01. No significant takers on the question. 

Let me rephrase, and perhaps reiterate...



Access DB sitting in a Novell server. 5 of us have admin rights to the 

program. The rest of the users have only read-write access. I thought 

that I would be able to work on objects within the DB provided no other 

person was working with that object. I found I cannot access any design 

changes or maintenance if ANYONE AT ALL is in the program.



Doesn't Access employ object level locking somehow? If so, where do I 

find it, and how do I go about employing it so that I don't have to 

"chase the whole user list out" before I can maintain anything????



Thanks for any light anyone can shed on this.



Regards,



Tom

Open the Access database and go to Tools -> Options and select the tab

Advanced.  Set the default open mode to shared and the Record locking to

Edited Record and check off Open databasees using record-level locking.



This is for Access XP (2002).  I am sure there is similar functionality

in the options of previous versions (at least as far back as 97).



Yehuda



-----Original Message-----

From: Thomas A. Benjock [mailto:TomBenjock@w...]

Sent: Thursday, August 16, 2001 3:25 PM

To: Access

Subject: [access] Access Object Level Locking?





To All,



Same question as posted 8/15/01. No significant takers on the question.

=3D Let me rephrase, and perhaps reiterate...



Access DB sitting in a Novell server. 5 of us have admin rights to the 

=3D

program. The rest of the users have only read-write access. I thought 

=3D

that I would be able to work on objects within the DB provided no other

=3D person was working with that object. I found I cannot access any

design =3D changes or maintenance if ANYONE AT ALL is in the program.



Doesn't Access employ object level locking somehow? If so, where do I 

=3D

find it, and how do I go about employing it so that I don't have to =3D

"chase the whole user list out" before I can maintain anything????



Thanks for any light anyone can shed on this.



Regards,



Tom

you may have to break the couple between the objects (forms,controls,etc.) 

and the data itself.



If a user is using a form within that database to edit a table while you 

might want to update the form, there would be a lock.  also, it is quite 

possible that many of the activities in your maintenance conflict with 

system level locks that the access db is itself using during the normal 

course of user business.



your solution (probably not the one you want) might be to create a 

stand-alone application that resides on the user's workstations that access 

your database on its server.  have the users make the data requests from the 

access database instead of using objects within the database make requests.



just an idea.  hope it helps.

dav





>

>

>To All,

>

>Same question as posted 8/15/01. No significant takers on the question. 

>Let me rephrase, and perhaps reiterate...

>

>Access DB sitting in a Novell server. 5 of us have admin rights to the 

>program. The rest of the users have only read-write access. I thought 

>that I would be able to work on objects within the DB provided no other 

>person was working with that object. I found I cannot access any design 

>changes or maintenance if ANYONE AT ALL is in the program.

>

>Doesn't Access employ object level locking somehow? If so, where do I 

>find it, and how do I go about employing it so that I don't have to 

>"chase the whole user list out" before I can maintain anything????

>

>Thanks for any light anyone can shed on this.

>

>Regards,

>

>Tom