Consurrent User Problems

[Mark]

I have created a concurent user Access system with a front end on each
user's computer and a back end sitting on a common server. I am not
using the user level security. I have check that the dbf is shared and
row level record locking is enabled.

More than one person can enter the system but the moment forms or
reports are accessed from the Switchboard error messages saying
somebody else has the table open in exclusive mode.

How do I keep this from happening?

Thanks for any help on this issue.

 

[Douglas J. Steele]

Do all the users have full access (Read, Write, eXecute and Delete) to the
folder on the server where the back end resides?

They must: the first user to connect to the database causes Access to create
a locking file (.ldb) in that folder, subsequent users need to update that
locking file, and the last user to exist causes Access to delete the locking
file.

 

[Mark]

Yes Doug, all users have complete access r/w/x/d access to the be
folder on the server.

Just for the record, most folks in our IT group think MSAccess cannot
be used concurrently and that is why this problem is occuring. Can
more than one person access the tables on a back end? This issue is
holding up implementation and I am totally stumped.

Can you think of any other "switches", "flags" or coding I might need
to set or tweak? Any books that might prove insightful?

Thanks..

 

[Larry Linson]

Yes Doug, all users have complete access
r/w/x/d access to the be folder on the server.

Just for the record, most folks in our IT
group think MSAccess cannot be used
concurrently and that is why this problem
is occuring. Can more than one person
access the tables on a back end?

Yes, Access is inherently multi-user. {I spent some of my career working in
or with IT departments, and I've never known any subject on which so many IT
people were MISinformed as on Access!}

Check once again to make sure the users have both Create and Delete
authority for the shared folder in which the database and its LDB file
reside.

Check to make sure that none of the users opened the DB in exclusive mode.
Create a desktop shortcut to open the DB, so you can specify the
"parameters" of the command line statement.

The Table supporting the Switchboard, if your switchboard was created using
the Switchboard Manager, should be local to each user's computer -- not
moved to the "Back End" with all the other tables. Personally, I find the
Switchboard Manager-generated switchboards to be more trouble than they are
worth (a complex solution to a simple problem, and don't ever use them
except to demo to a user group that the SM exists). I create my own, using
unbound forms, command buttons, and sometimes a few other controls to allow
user's to select the record or range of records they want to view and/or
edit.

Larry Linson
Microsoft Access MVP

 

[Tony Toews]

Check once again to make sure the users have both Create and Delete
authority for the shared folder in which the database and its LDB file
reside.

To add to Larry's reply. Ensure each person can create a .txt file in
that directory and delete it.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Tony Toews]

Just for the record, most folks in our IT group think MSAccess cannot
be used concurrently and that is why this problem is occuring. Can
more than one person access the tables on a back end? This issue is
holding up implementation and I am totally stumped.

Absolutely. I have clients with 25 people using the backend. There
are reliable reports of up to a hundred.

There are some things you must do mind you.

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

If the problem is for everyone when starting up the MDB then it likely
needs a decompile.

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Ron2006]

I have a more basic question. I do not know the answer, and will leave
it with the MVPs to answer.

In your first question you say:

"I have created a concurent user Access system with a front end on each

user's computer and a back end sitting on a common server. I am not
using the user level security. I have check that the dbf is shared and

row level record locking is enabled."

Are you truely linked up to a DBF instead of an MDB.?

MVPs: Does this make a difference? Can it make a difference.

Ron

 

[Tony Toews]

I have a more basic question. I do not know the answer, and will leave
it with the MVPs to answer.

In your first question you say:

"I have created a concurent user Access system with a front end on each

user's computer and a back end sitting on a common server. I am not
using the user level security. I have check that the dbf is shared and
row level record locking is enabled."

Are you truely linked up to a DBF instead of an MDB.?

MVPs: Does this make a difference? Can it make a difference.

Excellent question. I never noticed those three letters before.
<chuckle>

And I have no idea of the answer as I've never used dbf's for anything
but importing.

TOny
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm