I am wondering if there has been any progress regarding the preformance bug in the ODBC driver with batch updates?

(e.g.. UPDATE TextbaseName SET FieldName = 'Value' )

When updating multiple records, this bug causes application timeouts and can corrupt the data integrity of the app by leaving the textbase in a half-updated state. In an ASP.NET application, even with the Page and Connection objects set to infinite timeout, the ASP.NET worker process is recycled after 180 seconds, as it is considered to be deadlocked while waiting for the operation to be completed. On my development machine, updating 200 records takes almost a minute!

Any information regarding the status of this issue would be appreciated.

-------------------------------------------------
Nathan Mayr - DevActive Communications,
Web Application Development Services
White Rock BC, Canada
Email: nathan@devactive.com http://www.devactive.com/