Split Database with Synchronization

I am currently designing a database that will be used on a LAN and a number of remote laptops that may or may not have access to the internet.

I would like to be able to have a split database so that I can modify the front end without have to worry about bringing the data over to a new database. I already know how to accomplish this, I am just mentioning it to see if anyone can forsee any problems that I may have.

Now to get into Synchronization, I know how to accomplish this in a database that is not split by creating a replica. I don't know that I entirely like the way that it works but I can get it to work. The problem I am running into is when I split the database into two parts, and being able to syncronize the backend while using the frontend.

My other concern, Is this the best way to accomplish syncronizing the database with the situation that I have. I know I often design a database one way, to find out later that it would have worked better had I done it a different way. I am trying to avoid that realization on this database project.

Any help you could provide would be much appreciated. Thank you in advance for you time.

Hi Kevin,

Although you have gotten the synchronization to work in an unsplit database,
you should know that replication is not meant for anything but data (i.e.
tables), not queries, forms, reports, etc. Normally one would split the
database and replicate only the backend. When remote computers connect,
they synchronize their backend databases. They have a copy of the frontend,
which (like a normal frontend) is simply copied over when there are updates
to it.

An important note - you said 'laptops that may or may not have access' -
replication is only for computers that can connect (even if it is
infrequent). You cannot synchronize by copying files, the laptops need to
connect.

Some good resources on replication

http://support.microsoft.com/?id=190766 - white paper
http://support.microsoft.com/?id=282977 - FAQ

Also see
www.trigeminal.com - excellent replication site
http://support.microsoft.com/support...eplication.asp

If you have further questions, I'd suggest you ask in the
microsoft.public.access.replication group, as that's where the experts hang
out.
Good luck

--
Joan Wild
Microsoft Access MVP

Kevin McBrearty wrote:
I am currently designing a database that will be used on a LAN and a
number of remote laptops that may or may not have access to the
internet.

I would like to be able to have a split database so that I can modify
the front end without have to worry about bringing the data over to a
new database. I already know how to accomplish this, I am just
mentioning it to see if anyone can forsee any problems that I may
have.

Now to get into Synchronization, I know how to accomplish this in a
database that is not split by creating a replica. I don't know that
I entirely like the way that it works but I can get it to work. The
problem I am running into is when I split the database into two
parts, and being able to syncronize the backend while using the
frontend.

My other concern, Is this the best way to accomplish syncronizing the
database with the situation that I have. I know I often design a
database one way, to find out later that it would have worked better
had I done it a different way. I am trying to avoid that realization
on this database project.

Any help you could provide would be much appreciated. Thank you in
advance for you time.