We have a solution that has several databases. We us an interface that writes to all of the related records in the various databases. Example: A unique # is assigned to a case. That case will create records in DB1 DB2 and DB3, the unique# being the relationship. When a user opens the frontend interface they can write to DB1,2,and 3.

In FM 2 people can't be modifing the same record. Is there a workaround were they can.

We need the user to be able to go into the frontend and modify DB1 on one screen while another user is modifing DB2 on another screen.

thanks in advance for your help

2 cents worth:

Maybe you can use globals and scripts to put a buffer between actual modifications? Users could "submit" changes via button/script which then modifies for real?

--ST

As Steve T. pointed out, you could use a duplicate set of global fields to allow users to modify the data, then a "Submit" buton would move the data to the record.

I would not suggest this way, however.

This gets into the realm of clairvoyance, where computers are not very good at. Suppose the 2 users modify the same field with different data. The last person to post or "submit" their changes would wipe out any changes made by the first user.

Whoever solves this age-old database problem will become richer than Bill G. himself.

Unless you come up with a real complicated set of checks, calculations, priorities, error messages ("Your data submission was wiped out by another user."), it would be better to just let users know that only one person can modify or work on the same record at a time, and to wait until the other person is finished - it's safer that way.

Could you also add a timer that would remove a user from being inside a field, so others could then update it? I seem to recall a thread about that action from a while back, but could not find it. Anyone else know the location?

Kirsten Masse