URGENT - Only one user can access DB ?

[HJessen]

I have JUST distributed a front-end DB to a number of users here, and have come across a problem that makes the overall DB useless in their eyes.

I have TWO front-ends - one for individuals who can make changes to the information in the back-end DB, and another for those with read-only access to the data. Why this way? Mainly because of the items they can - or cannot - access on the switchboard(s). It is easier for me to track and control.

Anyway, if one of my read/write users is using the DB, those with read only cannot access their items (i.e. lookup forms, data display forms/information, etc.). I see that the r/w user creates an .ldb file, but why? How can I set it up for multiple users to see the data in the back-end?

Please help me as this is a top priority here, and this information is vital to some of the functions going on.

THANKS in advance!!! H. Jessen
"Now I know more, and I feel dummer"

 

[annsolomon]

You can have two different front ends and yet have all users log into (join) the same workgroup (ldb file). Try that and see if your problem goes away.

Ann

 

[mp9]

Just to eliminate the obvious, your r/w users don't open the database exclusively, do they?

http://www22.brinkster.com/accessory/

 

[HJessen]

TO: annsolomon -

I have NOT initiated any security on this DB - so whenever anyone signs on, they ar 'admin' and using system.mdw. Again, since I did not initiate security, that means everyone uses their own system.mdw file. Correct?

TO: mp9 -

The shortcut on the users desktops - which I distributed to them - does NOT open exclusive on the file.

- - - - -

Someone just mentioned that they wondered if it could be a network issue, since the authorities are issued by the network, not by MS Access.

Any ideas?

H. Jessen
"Now I know more, and I feel dummer"

 

[BBaggins]

What exactly do you mean by "those with read only cannot access their items "?

Do they get an error when the program executes a select query? Are they able to open the database?

Unless your program opens the database exclusively, it is inherently multi-user. No special steps are required from the database end. By the way, the first user who opens the database creates the ldb, regardless of their priviledges, and regardless of whether or not the db is opened exclusively.

What you DO have to do is trap concurrency errors in your program. For example, if two users attempt to write to records in the same table, the first user will be successful but the second will get an error. Your program needs to trap that error, wait a random amount of time (about half a second works) and retry the insert/update/delete that failed. It should do this quietly, so the users don't even know a conflict occurred.

Another thing you want to avoid in a multi-user Access app is the use of Table- and Dynaset-type recordset objects, and -- of course -- data controls. Stick with forward-only snapshot-type recordsets and do all your updates and inserts with SQL queries and db.Execute.

It works; I've got as many as 40 users sharing an Access db with no problems.