Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Multiple database sync

Status
Not open for further replies.

Sleepingweasle

Technical User
Feb 6, 2005
2
US
First, I’d like to thank all of the members here. I found many solutions here in the past.

I have 20 different teams that will each have their own copy of a database, with information specific to that team on it. The databases are identical, only the information in them is different. I need a way to sync each of the “Team” databases with its “server copy” of their database on our server, but the teams are not always on line.

What is the easiest way to sync the 20 “Team” databases with the server databases? All of the databases are in Microsoft Access 2007, and should update daily when they connect to the internet. I’d prefer this happens in the background, so it wouldn’t require any input from the user.

I don’t know how / if this can be done, so I’d appreciate any help with this. Obviously I don’t expect / want anyone here to do it for me, just please point me in the correct direction. Should I use Groove, Oracle, etc.? How should we set up the server? Our company is starting the server and database synchronization from scratch, they haven’t bought any software other than Office, but know they will need to. What software do you recommend, as well as what is a good source on information for that software.

Thanks for your help.
 
Well, in all honesty, if the only difference is the data in each database, then you've got a bad setup from the get go. What you need to do is use your SQL database - Oracle it sounds like in this case, and just use Access for your front end. That way, no syncing required, any update is made direct to the database. Of course, this is assuming network connectivity.

If you have to or just want to for some reason keep your current setup and just sync to the server, I'd suggest setting up a query which runs at open and/or at close and/or at some certain time or whatever... you could test using it on the server itself, or in Access. Just whatever fits your situation best, I suppose.

--

"If to err is human, then I must be some kind of human!" -Me
 
With just Access you can do this with replication. We do this at work. I have a back end database on the server with just the tables. Each user has a front end with the forms, reports, queries, and modules. If the user can touch the network with a good connection then they have a button that links their tables to the backend on the network. If they are away from the office and have a poor connection or no connection, they have a personal replicated back end. They then can work on their replica and either synch using vpn or synch when they return.

A2007 does support replication, but the replicated backends will be in 2003 format. Does not seem to make much of a difference. However, A2007 has introduced a lot of sharing of data through Sharepoint. I believe this will be the future for Access remote use. If you can hit a sharepoint site while remote this is another option. There does not seem to be a lot written on this yet.

If the teams are not on line and need to use the database then they will need to use some sort of replication. I have done this a lot because when my teams are in the field they are in the "field" with no connection to a data source. They may be in a remote location for weeks.

I can only speak on Access replication, I do not have experience with other applications that may do this better.
 
Thanks a lot everyone. I really appreciate your help. I'll try some of these out, and post my results when I have them.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top