If you look at cDataSource.Save(), there is code that loops through RS to find out update conflicts to generate error string. As I said, it is an ADO error and being treated as a regular error.

>>Yes. It is. In this scenario, ADO will throw an exception which will be trapped.
>
>Where does COMCodeBook handles this then if it is trapped? Where does COMCodeBook explain how this is managed by the developer?
>
>
>>
>>>How does COMCodeBook deal with errors such as the following:
>>>
>>>I have a web page that ask for a User Record based upon a key.
>>>The data is brought to the user for modification.
>>>They think about it for awhile and make their modifications.
>>>But while they are thinking someone else changed the data.
>>>Then web user presses the Save button.
>>>
>>>Does COMCodeBook controls just blowup with an OLE DB/ODBC error, does it report back that someone has changed the data, or does it even handle this type of error?
>>>
>>>TIA