Problems with a multiuser Access database.

G

Guest

I've built an order entry database in Access 2002 that I'm depoying in an
office with multiple users. Each user has a local PC with an XP operating
system tied into the company's network. I've split the database into a front
and back end. I've placed the back end on a shared network drive, and have
put the front end on the hard drive of each of the 7 user's PCs. With
multiple users in the application at one time, there seems to be significant
restrictions in being able to easily use the application without first having
other users close portions of the database. Have I done something wrong in
splitting the database?
 
O

Olden Doode

Lee said:
I've built an order entry database in Access 2002 that I'm depoying in an
office with multiple users. Each user has a local PC with an XP operating
system tied into the company's network. I've split the database into a front
and back end. I've placed the back end on a shared network drive, and have
put the front end on the hard drive of each of the 7 user's PCs. With
multiple users in the application at one time, there seems to be significant
restrictions in being able to easily use the application without first having
other users close portions of the database. Have I done something wrong in
splitting the database?
More likely to be something like someone has it opened exclusively
instead of shared, or that record locking is set to something larger
like page locking etc. that doesn't allow others access while the page
is locked. individual record locking is better.

Also if you didn't use a workgroup and someone is fiddling with tables
or queries or designs it might cause a problem as well, delays would be
the least of one's worries in this case.
 
A

Albert D.Kallal

. With
multiple users in the application at one time, there seems to be
significant
restrictions in being able to easily use the application without first
having
other users close portions of the database. Have I done something wrong
in
splitting the database?

Hum, I don't think so. You don't mention what kind of problems. However,
there is two things to check

first, make sure that everyone has FULL rights to the shared folder. When I
say full rights, I mean cerate, delete etc...all rights. If you don't give
users full rights to that folder, then often ms-access will kick into read
only, or single user mode.

The next thing to check is your record locking settings for the forms. For
example, if you set the record locking for a form to the whole table, then
all other users will NOT be able to edit that data in the table until the
first user gets out.

Another thing to check is the record locking setting

tools->options->advanced tab. Check the setting for default open mode (it
should be shared), and also ensure that you have record level locking. (if
that option if not checked, then page locking is used, and users can trip
over each other quite a bit easer).

Note that the "default record locking" setting is what your forms will use
as the default. So, changing that setting will NOT change your existing
forms. Hence, check the record locking setting used in the forms that are
giving your trouble.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Multiuser environment 5
Database Splitter: Update? 3
Multiuser problem 1
Sharing Database in multiuser enviroment 1
Splitting A Database 3
Networked Database 2
Joining a Split Database 1
Optimizing the database 3

Top