Lamar,

You can force the TABLEUPDATE() (check the help file). This will mean that the changes the other user made will be overwritten by the new data. This is sometimes desirable. You can also use CURVAL() and OLDVAL() to determine what changes were made and allow your user to decide whether to overwrite them or not.

>>>What are my options if ROLLBACK is not an option for my client.
>>>More Info: We take order over the phone and key them in. Many times the customer is not on the phone when we finalize the order. If the user clicks save and has a conflict ROLLBACK is not an option at all. Is this an all or nothing proposition.
>>>
>>>Thanks in advance for any suggestions.
>>
>>Do you mean ROLLBACK is not an option because you do not use transactions?
>>And what do you mean by conflict?
>
>Sorry, not enough info. I want to use transactions to make updates to the to the inventory file, but if someone
>else made changes to the same record I can't successfully do a tableupdate(). What I mean when I say ROLLBACK is not an option, I mean from a business standpoint. If you Rollback you don’t have the customer on the phone and you don’t have an order.