Multi-user scenarios, any pointers?

[Johan Myrberger]

Any pointers to "Multi-user scenarios for MS Access 2000 for dummies"?

I understand that this is possible, and probably involves a back-end and
front end DB etc. Any good information on such scenarios, incl.
alternatives such as replication etc, available?

Thanks
/Johan Myrberger

 

[Albert D. Kallal]

Here is a good link:

http://www.granite.ab.ca/access/splitapp.htm

 

[Mike Labosh]

Any pointers to "Multi-user scenarios for MS Access 2000 for dummies"?


Here's a pointer you can use for just about anything:

void *p;

Sorry, couldn't help myself.

I understand that this is possible, and probably involves a back-end and
front end DB etc. Any good information on such scenarios, incl.
alternatives such as replication etc, available?

Most often, multiuser Access apps work like this:

Table-only MDB on a file server (backend)

Everything-Else MDB with linked tables from the backend (front end) copied
to each user's machine.

While you can put the frontend database also centrally on the file server
and have the users machines point at x:\share\front.mdb, you will suffer two
serious drawbacks, so this is not recommended.

1. GIANT amounts of network traffic because not only is the data going
across the network, but also all the queries, forms, reports and code.
2. If you change something in the database design or break a form or some
code, everyone using it will simultaneously break, and your users will hate
you.