Branching and merging back into a Central FM db

[joseppic]

Hi,

We have the situation where people back at base need access to an FM db (on a LAN server).

People need to record into the FM db on their standalone tablets 'out in the field' and come back to base and get that data back into the Central DB.

There could be one or many users 'out in the field', so I'm not sure about merging two or more FM DBs back into the Central DB, or whether each 'man in the field' takes out a copy of the Central DB and they all get merged somehow back at base. The one/many people in the field will also need off-line access to the Central DB (i.e. a copy of this must be on their table pc too). Is there a prescribed way of doing this? Am I making any sense? Basically I need guidance to

the ideal architecture/methods of branching and then merging databases (retaining data integrity).

Thanks for any help.

Joseppic.

[BobWeaver]

There have been a number of threads started on this subject. Have a look at "file synchonization" topics in this forum.

To summarize what they say: You can do it as long as you define strict rules for handling all the problem situations. Eg, what do you do when two users remotely modify the same record etc. Which one is correct?