Challenging Puzzle

[wallyworld]

Here's the scenario: MONDAY - Employee A and Employee B work on and update a database using the same network at their office. TUESDAY - Both Employee A + B work on the database at home on seperate servers (Thus creating two different versions of the database). WEDNESDAY - Both Employee A + B return to the office and work on the same server BUT their databses are both different.

QUESTION: Can the two different databases be combined (meaning field entries) WITHOUT them overlapping eachother? ([ex.] There are 2 records in the database - Employee A updates record 1 and Employee B updates record 2. When they import to eachother's database Employee A overwrites record 2 with his old version, thus losing Employee B's work on record 2.)

If this makes any sense I would greatly apprieciate a response. I am using FilemakerPro 4 on windows XP. Thanks!

[QuinTech]

Hi, Wally, and welcome to the Forums!

I am a little confused. It seems to me that on Wednesday, A&B would not have different databases, as they would both be accessing the office server copy. They will have different data at home, so there will be three versions; but there needs to be a delivery mechanism, no?

Maybe you could make some sort of checkout system, where records 1-500 are exported to a new file (FileA) then deleted from the office server, and 501-1000 are exported to another new file (FileB) and deleted from the office server. FileA and FileB go home with the appropriate people on Tuesday and are returned on Wednesday, to be re-imported into the office server.

Another option is to use remote desktop software, either something like Citrix or something like PCAnywhere. This would be my preferred option. Having multiple copies of any database, even following best practices, puts you close to a problem.

HTH,

Jerry

[CoZiMan]

Well, I use something like this that is scripted for multiple users on standalone systems.

They generate a standard text file, exporting the same fields AS SCRIPTED to a standard FILE NAME and LOCATION. Then import FROM the standard location the standard file name and UPDATE matching records or add the new ones.

Does this make sense? Each user can have their own copy of the DB. The Office copy is just 'another user' even if it's run from a server.

Ok?