Replication & Security

[Guest]

Question, how do we let multiple people
with different security levels access the database at the same time. Maybe
my understanding is wrong, I thought multiple users could not access the
database at one time without using replication, is this correct.?

 

[Rick Brandt]

Question, how do we let multiple people
with different security levels access the database at the same time.
Maybe my understanding is wrong, I thought multiple users could not
access the database at one time without using replication, is this
correct.?

AACK! Of course not!

Replication is used relatively rarely and is quite tempermental. TONS of
Access apps are used by multiple users at the same time. The two have
nothing at all to do with each other.

Replication is for when multiple users want to use *different copies* of the
same database and then later want to merge all of their changes back
together.

Multi-user is simply the act of more than one person editing data in the
SAME database at the same time.

 

[Joan Wild]

You do not need to replicate in order to have multiple users using your mdb.
Replication is for circumstances when a user may not be always connected to
the network (like a salesman with a laptop), and they then need to
synchronize the data changes once they return to the office.

In a single networked office, you don't need replication. Access can easily
be used by multiple users. I suggest you split the database and put the
backend (just the tables/relationships) database on the server. Give each
user a copy of the frontend (all remaining objects) database. The frontend
would contain links to the tables in the backend.

 

[Keith Wilby]

Question, how do we let multiple people
with different security levels access the database at the same time. Maybe
my understanding is wrong, I thought multiple users could not access the
database at one time without using replication, is this correct.?

I already answered this in your other thread. Please don't start multiple
threads on the same subject.

Keith.