>Your situation depends on what kind of buffering you use. If data is not buffered at all you shouldn't have concurrent problems on the same workstation. Surely you must enforce integrity rules with appropriate error traps, write own refresh methods for multi-form interface (normally you should refresh when you activate a form. Also would you consider using of private data sessions? Otherwise any pointer moving will be effected throughout all forms and may fire field/record level rules, it can be effected manifold negatively if you have buffered data.

Tks for the response, my specific situation is like this:

Two forms are referring to the same Table, the first one used to update data records and the second one is used to show the updated data under a Grid. The updated data is to be refreshed and shown in the second Form immediately.

Under these circumstances, I have to set both record buffering and default data sessions (I don’t know how to use private data sessions to do the trick, if it can be done at all). After updating records in the first Form, I activate the second Form, like you said, pointer movements inevitably fire field/record level rules, resulting in an error.

How can I prevent this problem?