Results 1 to 6 of 6
  1. #1
    Join Date
    Jan 2004
    Location
    St. Petersburg, FL
    Posts
    2

    Unanswered: ADO Using ODBC vs. OLEDB

    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?

    Any input would be appreciated....Thanks

  2. #2
    Join Date
    Dec 2003
    Posts
    454
    Can you post the error message you got?

  3. #3
    Join Date
    Feb 2002
    Posts
    2,232
    Is this an asp or asp.net application ? Yes and please post the errors and the code it is failing on.

  4. #4
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    It definitely sounds like all your back-end code sits on the front-end, right? You would save a lot of time if instead of cleaning it up try to move to where it belongs, - back-end.

  5. #5
    Join Date
    Jan 2004
    Location
    St. Petersburg, FL
    Posts
    2
    Thanks for responding to my post.

    I am using standard ASP pages not ASP.NET.

    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.

    Thanks

  6. #6
    Join Date
    Jan 2004
    Posts
    31
    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 :

    http://www.adoanywhere.com/forum


    Mike.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •