I have build at Access database which is running on a small network (5
computers) and I am having stability problems: when someone on one
terminal enters a client (selects a record) via a form, that client
comes up on the other screens, displacing the records that they
selected. How can I prevent this? It is as if the system is sharing
bits of memory between all of the computers.

The database is running on Access 2002. It is available on a network
and the database has been split. The 5 terminals have identical
versions of the front end of the system. The database is small: it
contains only a few hundred client records.

We were originally running the system with no locks, and have now put
locks on all of the forms (using ?edited records?). The system seems
to be a little more stable, but other people?s records still flash up
when one of them changes data in a record.

Also, if I try to run reports (using buttons/macros in the forms) they
may select the record that is open on one of the other computers. If I
put locks (edited records) on the reports, an error message comes up.

Can anyone suggest how I can resolve the problem? Do I need to put
locks (?edited records?) on all of the queries too -- or perhaps just
the temporary files that are used when selecting a client?

---

Request for Question Clarification by dewolfe001-ga on 11 Nov 2003 11:08 PST

Is it possible to post the database somewhere (even without much of
its data) so that it can be looked at?

The multi-user issue is something that Access is infamous for. There
are two ways around it:
A) Set up a version of the database on each desktop and have them
connect to the main Access database via ODBC, so they have a client of
forms and functions; but the data is in one place.
B) Run a web service, an Intranet, from your server. Personal Web
Server or Internet Information Server are two easy options for a
Microsoft platform. Then build the forms as HTML and use ASP to accept
the information and add it to the database. This is a much bigger task
than option A, but the request-response model means that the database
will be usually "dormant" and cut down on database locking. With this
model, you could have dozens of concurrent users.

---

Clarification of Question by edwarduk-ga on 13 Nov 2003 04:36 PST

Thank you for responding to my question.

The second option you suggest may be the best but it is not practical
in the circumstances. We must work on the first...And this is what I
need help with.

As I said in the question, the database is split. The data is in one
place (database.be) and each terminal has its own database which is
linked into the master. These are all the same.

I don't know whether it will be possible to mail a copy of the
database. I need to seek permission. Unfortunately, I am away for
three weeks as from tomorrow (14th) and I will have very limited web
access. So can I get back to you in 3 weeks? I may then need advice on
the 'ODBCConnectStr' property and pass-through queries (I don't know
if this is what I am already using!) I have looked at the Access Help
on ODBCConnectStr Proprty but can't claim to fully understand it.