How long does it take to sync?

[Brambojr]

I am planning to create replicas of a set of small front end db's and make a set for each computer in our distribution center (~30) that will be saved to its own hard drive.

A large part of my motivation is that it could be a great way of distributing design changes. It would also prevent file sharing problems between Win98 and 2000.

I have two tables, one in each individual replica and the other linked to the back end - both have a version. Upon opening the Db checks to see if it has the most current version, if not synchronize.

Big question: I am talking about front end databases all tied to the same back end. Each Db in the neighborhood of 5 meg distributed over a 10/100. Does anyone have any idea how long this could take? I need to work out a lot of details and let my unsophisticated users remain unsophisticated.

Any help would be very much appreciated. Brambojr

 

[sathandle]

Better idea - have the users replace their front-end with a new file that overlays. Your theory is correct to have the matching version # in both the front end and the back end.

Synchronization is best used on Data and not for interface file. Do the version check as you have set-up. When the versions have been updated, have access run a batch file or open an html page that the user selects to update. After the user interaction, a new fe is copied to your user.

Good luck!!


definition of 'less behind': "not fully caught up, digging out slowly, one-week delay to "The IT hit the fan."

 

[psemianonymous]

The method I use for auto-updating is adapted from

http://www.abcdataworks.com

(check developers->Batch file deployment). There are other methods, but my big selling point on this one is that it is extremely simple to implement and update.

And yes, having each user keep the front-end on their local machine will reduce network traffic.