Allow multiple users to enter data to a table?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an access program set up on our network. As many as six people are
entering data at the same time. They are using a form connected to a table.
The problem is that the program will only allow one user at a time to enter
data into the form. If the form is open on more than one computer, it only
allows data from the computer that opened the form first. How can I get
around this?
 
1st advise doing this on a copy
Under Tools Menu, select Database Utilities, Database Splitter. This
creates a 'frontend' and a 'backend'. These are linked together on the
network (forms and queries in the frontend for users and the underlying
tables are the backend which hold all the data). This has worked well with a
small group 3-4 people.
 
I have two linked databases. Everything works okay in both programs as long
as one person is using it at a time. The problem is if more than one person
has the same form open at the same time, it only accepts data from one user.
The other users will submit there data, but the table does not accept the
data.
 
bgarey said:
I have two linked databases. Everything works okay in both programs
as long as one person is using it at a time. The problem is if more
than one person has the same form open at the same time, it only
accepts data from one user. The other users will submit there data,
but the table does not accept the data.

As suggested (and I can't tell from your description if you already have
a split database system) multiple user databases should be split with a
front end for each user on their own machine liked to the common back end
data.

Make sure that no user is opening the database in exclusive mode.

The other problem is record locking. Depending on what version of
Access you are using it may be a bigger or smaller problem. If two users
are editing data that is on the same "page" the first one wins and the later
ones are rejected. A page may have more than one record.

I will add that I have had to force batch processing from the front ends
under certain situations.
 
Back
Top