Question : VBA Code for Indirect Back End Synchronization Over VPN?

Hello ~

My client needs a reliable way to synchronize an Access 2003 back end database over a VPN running Small Business Server 2003, which enables mapping to Windows.  Based on earlier posts, it seems Indirect Synchronization offers the most reliable way to minimize data corruption.

Is there someone out there who can offer the VBA code or the structure for accomplishing this?

For example using:

db1 residing on C:\

db2 residing on H:\

I recognize this may be a tall order.  I appreciate your thoughts.

Best Regards, Jacob

Answer : VBA Code for Indirect Back End Synchronization Over VPN?

For what it's worth I did a little testing just to see what would happen with a replicated database with hundreds of thousands of records that I was synchronizing with another replica.  During the synch I deliberately ended the task just to see what would happen.  Though I certainly don't recommend it, I was surprised to find that both copies, replica and master alike survived w/o any problems at all.  The only thing that happened was the data being passed had to be resent.  

To be honest I figured I'd have to do a compact/repair at least but as it turned out I didn't even have to do that.  As for why the replica wasn't confused that is less of a mystery.  Replicas store all their changes, design and data alike in one great big BLOB.  If the BLOB doesn't arrive in tact access regards it as a failed transmission and proceeds as though it were never sent.  Hence, even direct synchronization offers some security.

As for Peter57r's comment he is correct.  Replication Manager comes with the Developer tools CD.  I'm assuming you have that if you're intention is to set up a hub.  Bear in mind that that Hub needs to be am Windows 2000 Server (So far as I know Windows 2003 does not provide any support for Access Replication (at least if you intend to use it as a hub) and I doubt that Microsoft has any intention of getting Server 2003 to provide that support in the future.

Rick