>Hi,
>
>I am writing a application with VFP7, SQL-Server and remote views. I have a general problem:
>
>There is a saved invoice with one master record (M) and one related child record (C1). At the same time two different workstation are requering the data for this invoice from the SQL-server (M1,C1). The first workstation adds one child record and saves the changes back to sql-server (M1,C1,C2 on sql-server and workstation 1; M1, C1 still on workstation 2). After this, the second user begins to edit the out-of-date invoice (M1,C1) with one child record. He adds also a detail record (C3) to existing date (M1,C1) and saves the changes back. The overwrite (tableupdate) is enforced.
>
>What do you expect what is saved ?
>
>I think, the correct answer should be M1, C1, C3. But it is M1, C1, C2, C3.
>
>If the user prints after saving f.e the invoice with data M1, C1, C3 will be
>printed. But stored on sql-server is M1, C1, C2, C3.
>
>I am sure, that is a standard problem of any application. Is there any other solution for that problem ? Or is that a disadvantage of client/server against record locking ?
>
>Thank you,
>-Andreas

Andreas;

Record locking is not limited to client/server as it is a part of file/server also. One of the things you must agree upon are business rules as to how records will be treated that are in the state you defined. You can allow overwriting or alert the user that changes have occured to the original record. This is a real problem and has many different solutions based upon user requirements.

Tom