Databases in multiple locations - lagging servers

ccondran08

Registered User.
Local time
Today, 10:40
Joined
Feb 27, 2014
Messages
58
I am working on a project that has 2 databases located in different locations (Australia and Korea) which is due to the lag in accessing the information from one central server location.

At the end of each week, an excel export is done from one database and is sent by email to be appended to the second database (unique fields to the first database only), the second database is then exported and send by email to be appended to the first database (unique fields to the second database only) so that both databases contain the same information.


I believe this process was the best idea at the time by previous staff members but now I am rebuilding the database and want to come up with an easier and more effective way of allowing people in different locations to be using one database but not having any problems with lagging due to computer servers being located in different locations. Any suggestions would be greatly appreciated.

:cool:
 
Are you restricted to using only Access as the backend?
 
In a way I am restricted to using access as the backend, but if i can justifiy a new and quicker way that it can be done better for everyone then i can convince them otherwise.
 
Access and Sharepoint server is one option you can look into.

How is the backend connected at the moment? Does your company have some shared folders between Oz and Korea?
 
Sounds like the sharepoint might be the go. There are shared folders between Oz and Korea, but there is a 4 minute lag between when you want to access records and save etc...there are 5 people in each location who use the database so is causing the problem. Do you think the Sharepoint server will be quicker and managable ?
 
Use one backend. Run the front ends at the other location on Remote Desktop (AKA Terminal Services) hosted at the same site as the back end.
 

Users who are viewing this thread

Back
Top Bottom