>>Hi Hilmar:
>>I know this function may procudte many conflict,is there a method to avoid it?
>
>Sorry, I don't understand. What function will cause what kind of conflicts?
>
>Hilmar.
On second thought - I assume you are not talking about a specific function, but about sharing DBFs in general.
This can basically cause two kinds of conflicts.
1) If one user uses a table exclusively, another user can't access it. I already gave the solution: open the table SHARED.
2) It may be possible that two users try to edit the same record. This can be solved through record locking (see rlock()), but the preferred method (in Visual FoxPro), is to use, at least most of the time, optimistic buffering (see: CursorSetProp("Buffering"), TableUpdate(), TableRevert()). With optimistic buffering, if another user saved changes after I started editing, TableUpdate() (with the default options) will fail, and I will have to start from the beginning (for this particular record).
HTH, Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
