Two location database

[allison]

I have a company that has two locations. I want them to use the same
database. I split it. Now do I just make a replica of the front end and
add the switchboards that I want to them separately? Or do I do it all
from the same front end? I am VERY new at this. I am a little confused
on how to tie it all together. I want them to use the same sub
switchboards. Do I need two heads to for the same beast?

 

[John Vinson]

I have a company that has two locations. I want them to use the same
database. I split it. Now do I just make a replica of the front end and
add the switchboards that I want to them separately? Or do I do it all
from the same front end? I am VERY new at this. I am a little confused
on how to tie it all together. I want them to use the same sub
switchboards. Do I need two heads to for the same beast?

If you're using replication - DO NOT!!! replicate the frontend. Only
the tables should be replicated. You can have as many frontends as you
need, all copies of the same master frontend; each user should have
their own copy of the frontend at either site. If you wish, you can
have different frontends at the two sites; there's no need to
synchronize them, just so they both are properly linked to the tables.
After all, the frontends don't contain any *data* - just tools to view
the data.

The backend should contain the tables. Access does not work well over
a WAN (Wide Area Network) so each location should have its own
replicated backend; you'll need to use internet synchronization to
keep the data the same between the two backends, at some suitable
schedule.

John W. Vinson[MVP]