Thanks, Your answer was very useful to me.


>>I'm using VFP 6.0 on Windows 98
>>
>>I have no idea when using
>>TABLEUPDATE(.T.,.F.) (Default) or
>>TABLEUPDATE(.T.,.T.) (With Force clause)
>>
>>I haven't find any kind of useful information about this.
>>Thanks in advance
>
>Carlos,
>
>Rule of thumb (which can be not true but usually is true). Use the force option ONLY when you know absolutely that you don't care what any other user may have done and you believe it is right and just to blow away everything that any other user may have done to the records or records.
>
>The force option ONLY affects the Update Conflict situation. That is when a user is editing and then tries to save and VFP finds that another user has changed the records during this user's edit. Force true will write past the error, while force false will honor the error and cause the TableUpdate() to return .F. indicating that the update failed.
>
>The only place I have ever used force true is in a conflict recovery method that attempts to fix any field level conflicts and then attempt the update again. The retry of the update has to Forced in this case as the update conflict would still occur.