[AccessD] How to prevent a mess

David,

Thanks very much for the reply.

I might try indirect synchronization if my client had a server. He has Windows networking set up in his office...just peer-to-peer, no server of any kind.

I've looked through the documentation for Replication on MSDN already. It hasn't been very helpful to me. There just seems to be a dearth of information that is instructional or analytical rather than feature-oriented, like the MSDN site.

Just to fill in some blanks, my client has Windows XP workstations at his office with Windows networking. There are a half dozen people with laptops that roam around the state that do data entry in my new application. This data needs to be merged with the master database at the home office periodically...there's no need for immediate updates. That's why I thought I could send CDs back and forth. The data that's entered includes GIF photographs stored in one of the Access tables...thus, the amount of data being replicated could be substantial.

I don't want to make a mess out of things, that's for sure...but I'm at a loss to come up with a workable plan for my client's situation. I'm going to look at Kaplan's replication tool to see if that might help.

I don't suppose there's a chance that the Access database could be moved to a web server on a web host and have replication performed in some fashion?

Regards,

Steve Erbach
Scientific Marketing
Neenah, WI