June 14, 201015 yr I have a local server based version of a filemaker database that all of our inside sales and support people run, but out sales people also take a copy of this database with them on the road as a runtime solution. There are 4 main tables in this database get updated by our people on the road. Meanwhile the people back at HQ are also modifying the data. So the question is twofold - what is the best way to merge these two databases together or 2) is there a better way to build the database with a minimal amount of tables to make the merging process streamlined. RIght now I do it by script based on record ID number and modification date, but sometimes one record is being modified both at HQ and on the road and when the merge happens - something gets lost from one side or the other. Any advice would be appreciated.
June 14, 201015 yr Best option: get rid of the runtime copies and get the sales people to connect to the main database through mobile broadband. Synchronisation is difficult, and it gets complicated mighty fast. Look into the SyncDek solution. http://www.worldsync.com/syncdek/
Create an account or sign in to comment