Multiple User Question

  • Thread starter Thread starter robsix
  • Start date Start date
R

robsix

I have just started working with Access in the past several weeks an
realized that there are significant limitations with multiple users.

How do I allow the records from tables to viewed and written by al
users online? It normally says that it won't let me save anything
though I feel as if its possible to get around this message. (I mea
would microsoft really release an "office" product that is meant fo
small businesses only?)

Anyway, this may not be the place for this post but I felt as though i
would be a good place to get a response. Where can I go to learn abou
this kind of thing
 
If your database tables and user interface forms and reports are in the same
database, then Access will not allow you to save any data changes. But, if
your data is in a separate database, you should be fine. When you build an
Access application, you should actually create two linked Access databases:
one for the user interface (forms, reports, queries, etc) and the other for
the tables. This has many benefits, including allowing the database to be
centrally located. Also, when you perform an update to the user interface,
you don't want to concern yourself with the possibility that data could be
lost.

Microsoft included a menu item under Tools -> Database Utilities -> Database
Splitter (or some sort of wording like that) that will actually step you
through the process of moving your tables into a new database and then
automatically linking those tables.

Microsoft designed Access 2000 and newer to not allow any changes when more
than one person is using the Access database. The split database scheme
will, however, allow the data changes to be saved.

Chris Darnell
 
I have just started working with Access in the past several weeks and
realized that there are significant limitations with multiple users.

How do I allow the records from tables to viewed and written by all
users online? It normally says that it won't let me save anything,
though I feel as if its possible to get around this message. (I mean
would microsoft really release an "office" product that is meant for
small businesses only?)
Click to expand...

How many users are you considering? Will all users be updating the
database simultaneously, or are most of them just reading data?

As a rule of thumb, fifteen to thirty users updating concurrently
should be managable with a properly designed application (there will
be some update conflicts, particularly if two users attempt to update
the exact same record at the same time). Upwards of a couple of
hundred read-only users should be managable.

It's vitally important to use the Database Splitter Wizard to split
the database into a "backend" - a shared database containing nothing
but the tables - and "frontend", the user interface with the forms,
reports, queries etc. Each user should have their own copy of the
frontend linked to the backend tables.
 
Back
Top