>I was under the impression that you are using SQL Server. I never tried to use COM Codebook with foxpro table so can't say much there. I am sorry if I wasted your time.

Thats OK, it still is an ADO recordset that is used. It is jsut that COMCodeBook's docs do not even talk about this issue from VFP, SQL Server, or even Oracle backend. Kind of frustrating.


>
>>>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.
>>
>>So what you are saying is that COMCodeBook has code in place and operational to handle and report back a problem such as table is unavailable or data was changed prior to this change? If so then why does the COM just stop (blowup with an ODBC error) when I lock a record from the command window before a Web COM using COMCodeBook tries to update that same record. I am testing COMCodeBook out as a 3 tier solution and this aspect of data updating does not seem to be covered by any of the COMCodeBook documents. The indications I get from other sources is the COMCodeBook did not take their code this far and that I would have to create my own error reporting system when data update conflicts occur. I was hoping that they were wrong, but so far no one has shown me any code or examples that dispute what they said. So if you think the Save method is already checking for this, then why is my senario failing with ODBC errors using COMCodeBook as is?
>>
>>
>>>
>>>>>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