Setting up replication with access front end

[John]

Hi

We have an access app (front-end+backend) running on the company network. I
am trying to setup replication for laptop users who go into field and need
the data synched between their laptops and the server upon return to the
office. I am planning it this;

Move all access tables to sql server and then link the tables to access
front-end mdb app (using odbc?). Copy the same setup (access front end + sql
backend) onto each laptop. Setup replication between the server sql server &
each laptop's sql server. My question is; would this sort of setup work? Is
there a better way to do this?

Thanks

Regards

 

[Alex White MCDBA MCSE]

Hi john,

answered your question in microsoft.public.sqlserver.msde group, please try
to avoid cross posting as it becomes difficult to track.

 

[Douglas J. Steele]

Replication is never recommended for front-end databases, only for the
back-end. Copying the front-end is definitely the way to go.

 

[Sylvain Lafontaine]

By itself, Access as a Backend is also offering the possibility of
replication. I never worked with it but before trying to transfert your
database to SQL-Server for taking advantage of its replication behavior, you
should take a look at what Access is already offering.

Also, many people have find that using their own procedures for
synchronising data between a field user and a central repository has its own
advantages for many scenarios.