I apologize for posting a thread that has most likely been covered in some detail. However I still am not finding any real good solutions to this so, thought it was worthwhile to start a new one:
I have created a database for a company that has two branches; one in Seattle and one in Florida. Originally the database was intended for the Seattle location, now they want to share it with the Florida branch as well. They have tried doing so by placing it on the network in a shared directory. They are connected by a DSL line, specs of which I am unsure. They were unhappy with the performance of the database when used at the remote site (Florida).
All of my research seems to indicate that MS Access does not work well as shared across a WAN and that corruption problems could result from trying to do this. Basically it appears to me that sharing across a WAN is not a good idea even if they were to beef up their bandwidth.
There are really only two main tables that need to be syncronized between the locations. I am working on a solution whereby they will use the send object command to send an email attachment with two text files representing the data in the two tables. I have tables linked to the text files (after they are moved to the correct folder on the PC) and then append queries will appent the data to the respective tables.
I have tested this and it can be done, and I also believe it is fairly straightforward for the end user.
But...I really do not care for that solution very much. It would seem to me that it would be best to have them actually working on the same database.
So, my question is...what is the best way to handle this scenario?
Thanks!
I have created a database for a company that has two branches; one in Seattle and one in Florida. Originally the database was intended for the Seattle location, now they want to share it with the Florida branch as well. They have tried doing so by placing it on the network in a shared directory. They are connected by a DSL line, specs of which I am unsure. They were unhappy with the performance of the database when used at the remote site (Florida).
All of my research seems to indicate that MS Access does not work well as shared across a WAN and that corruption problems could result from trying to do this. Basically it appears to me that sharing across a WAN is not a good idea even if they were to beef up their bandwidth.
There are really only two main tables that need to be syncronized between the locations. I am working on a solution whereby they will use the send object command to send an email attachment with two text files representing the data in the two tables. I have tables linked to the text files (after they are moved to the correct folder on the PC) and then append queries will appent the data to the respective tables.
I have tested this and it can be done, and I also believe it is fairly straightforward for the end user.
But...I really do not care for that solution very much. It would seem to me that it would be best to have them actually working on the same database.
So, my question is...what is the best way to handle this scenario?
Thanks!