Multiple Back-ends

[Jonas G]

For the company I am doing my thesis, I developed a tool in MS Access for monitoring sales data, customers, employee data etc…
The tool is working with a front-end database, installed locally on every PC and a Back-end on the company’s server ( Located at city Genk)
The tool is working smooth on the location in Genk.
But then the problem occurs when this tool had to be used on an other company location, 100km from the server (Antwerp); the waiting and loading times are very long, even for the smallest data.

Obvious this is because the companies network from one location to another is too slow. But because of financial reasons I’m looking for a software solution.

An idea is to create a Back-end server for each location, for all local data and one general back-end server for unique data ( for instance: there has to be a unique calculation number for each calculation made in the entire company).
I think this will decrease waiting times for some data, but not all…

Or does anyone have an other idea?

 

[boblarson]

I had a similar problem having to have one backend in our Main office in Sacramento, California and one in our satellite office in Portland, Oregon. I wound up using Replication. Plus, since I had Microsoft Office 2000 Developer's Edition, I used Replication Manager to manage the synchs which I set up to do every 15 minutes.