I am working on a large ASP application(s) which uses SQL Server 2K on the back end, ADO 2.7 for Data Access. The current connection strings are setup to use older ODBC drivers. I wanted to change them to OLEDB for performance gains and better support in the future.
The problem encountered is that once the driver is changed the pages become riddled with errors. There are many piece of ADO code that are supported using the new driver. Many are cursor issues or code dealing with identity columns.
Has anyone else gone through this process?
Is there a comprehensive listing of those methods that are not compliant between these two drivers?
The applications I am working with are comprised of roughly 10K pages altogether. There are many errors that occur and I am able to address them as they arise. It really has to do with a lack of support from one driver to another through ADO.
I really was looking for some resources on this topic not solutions to specific code errors.
If I listed each error and code sample here it could take a long time.
One place you might find useful is the recordset.supports method, it will tell you if a particular method is supported by the recordset or not.
You will find differences with transaction handling too I expect.
The dynamic recordset & connection properties change too.
You could get a copy of Adoanywher browser, it displays the supported functionality of your recordsets and allows you to open multiple connections with multiple recordsets. Full support for transactions. It displays all available recordset and connection properties.
I basically use it to compare drivers just as you are attempting to do.
The browser is currently free if you register quickly at the forum :