>In an application, multiple forms would be used from one work station. The forms would refer to the same table, opened under default data session in data environment.
>
>While there is no problem with the data structure and the data integrity, updates in one form would not instanteously reflect in the other form(s). Is there a general guideline for handling such a process?
>
>Additionaly, when data field rules are violated (i.e., a new data refering to a new master domain record) of in performing updating process in a form (say, a transacting process), I would attempt to bring in the relevant form (say, a maintenance process) to augment the data domain, data crash would also result. Which form method I could use to control the concurrent form switching while accessing the same set of closely knitted data files?
>
>I am new to the concurrent form concept in VFP and the foregoing problems have been a big headache in our design. Any suggestion would be appreciated.

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.