For example, the Join Data example is built around an ADODataset component that uses the previous SQL join. You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions.
It seems to be working fine when I execute the Stored Procedure once.If I run the same stored procedure immediately for multiple times, I am getting the following error.[OLE/DB provider returned message: Row cannot be located for updating.Some values may have been changed since it was last read.] OLE DB error trace [OLE/DB Provider 'MSDAORA' IRowset Change:: Set Data returned 0x80040e38: The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.]. For example, should the insert of a row into the previous join result in a new product and also a new supplier, or just a new product?
The Client Data Set/Provider architecture allows you to specify a primary update table (and advanced features actually not covered in the book) and also customize the updates' SQL, as we partially saw in Chapter 14 and we'll further explore in Chapter 16, "Multitier Data Snap Applications." ADO supports an equivalent to cached updates called batch updates, which are similar to the BDE approach.