Multiuser sharing problem

[dirkg]

Hi,

In a client-file server application I made in Access, I have quite some problems with sharing the central database when multiple users are logged on to it via their Access-client application. I assured though that the links do not have the property to open the database exclusively and also no user has the permission to open the centraldatabase exclusively. Still I very often get errors like

N° 3734: The database has been placed in a state by user 'Admin' on machine 'LDB08164' that prevents it from being opened or locked.

N° 3033: You do not have the necessary permissions to use the 'Server\\Directory\CentralDB.mdb' object. Have your
system administrator or the person who created this object establish the appropriate permissions for you.

N° 3045: Could not use \\Directory\CentralDB.mdb'; file already in use.

These errors occur in procedures where I use the DLookup-function. Is it possible that these errors are caused by functions like openrecordset, in other words that functions like these overrule the lack of authorisation to open this database exclusively?

Any help is appreciated a lot since this is a very ennoying problem for the users...


Greetings,


Dirk

PS: I'm using Access 2000

 

[JoeMiller]

In order for mutliple users to work properly and consistently in access you need to setup a common workgroup (an MDW) via the workgroup administrator for all people that will be working in the db. Then those people need to access the database using that MDW file so that multiple users can be in there together and not step on each others toes.

HTH Joe Miller
joe.miller@flotech.net

 

[DOA]

Question for Joe?

Would it be better to code all of the forms to be unbound and have them do more of a transaction style. Add/Update/Delete. This way if s/he every wanted to take this to SQL or... then s/he would only have to change the calls to the database.

Although it is more coding is it better?
Thanks

 

[JoeMiller]

That question depends on a couple different things that need answering:

1) How many users?
2) How many records?
3) What version of Access?
4) What kind of application?

Access is designed to be a front-end for MS SQL server, but the newer versions do it more effectively. Unless this is a GIGANTIC database with hundreds of users that has a high transaction rate using an older version (97 or less) then I'd say it's not totally necessary. The difficulty in writing it so makes the ROI pretty small. But some developers prefer to code that way, and far be it from me to tell them how to do their job.

The main reason people do it that way is record locking can be controlled much more that way. But the newer versions support much of the advanced locking that MSSQL does making this coding style less of a requirement. However, if you can pull it off then there is definite benefits in speed for the user and control for the developer.
Joe Miller
joe.miller@flotech.net