can multiple users write to a database simultaneously?

[steve]

I want to create a database that allows multiple users to access and write
simultaneously, is this possible and how do I do it?

 

[Wayne-I-M]

Hi

Many people can write to a DB at the same time but, this may cause problems
(unless you take actions to prevent the problems)

You should split your DB so that the data (in tables) is stored somewhere
(the back end) and the other "bits" (forms, etc) are stored on each seperate
computer used by the users (the front end).

The backend does not need to have access loaded (our main server has almost
no programmes - well very few any way) but it is used like an external hard
drive to store the data.

There are many posts concerning very simple methods of doing this (access
has wizards to assist you). Search this forum or google on "splitting a
database"

 

[joecosmides]

I want to create a database that allows multiple users to access and write
simultaneously, is this possible and how do I do it?

Create a database with only the tables in it. I usually call mine
suchandsuch_BE. The BE tell me it's the back end. You can call it
whatever you wqant really. Remember only the tables go into this
database. Move this database to a shared folder. On each computer you
plan on using the database you need to create a mapped network drive
with the same drive letter. For example I created a mapped drive to \
\joespc\db (db is the shared folder by the way) and I used the V:
letter for that mapped drive. You must use the same V: letter for
every person's PC who will connect to that shared folder.

Next, create another database. Mine would be called suchandsuch_FE,
meaning Front End. Again, call it whatever you want. This is the
database you will use to add your forms, queries, reports, or anything
else, etc. Do not add any tables to this database. Now in this
database, go to File, Get External Data, Link Tables, then choose your
mapped drive V: and pick the back end database you created earlier.
You will see all of the tables you created and you can select all of
them. Keep in mind that if later on you want to add more tables or add
more fields to those tables you must always go to the BackEnd database
suchandsuch_BE and do the work there. You cannot do this using the
front end because the tables re linked and it just won't work. Once
you are done you can copy the font end to each user's pc and put it
anywhere you want, I happen to use the desktop and most people do as
well.

If you've already created the database with tables, forms, queries,
etc, you can go to Tools, Database Utilities, Database Splitter and it
will remove your tables for you and create the back end.

 

[joecosmides]

Also, don't forget that if later on you decide to add a new table to
the back end database that you will have to go to your front end
database and go to File, Get External Data, Link Tables and add the
new table

 

[Beetle]

plan on using the database you need to create a mapped network drive

with the same drive letter. For example I created a mapped drive to \
\joespc\db (db is the shared folder by the way) and I used the V:
letter for that mapped drive. You must use the same V: letter for
every person's PC who will connect to that shared folder.

If you used UNC path naming, instead of drive letter path naming, then
you wouldn't need all that extra work.

 

[a a r o n . k e m p f]

yes--- in other words, linked tables are a complete and utter pain.

you should just upsize to SQL Server and use ADP-- then you won't need
to deal with any of this hassle

-Aaron