|
John, Using them from where? Some applications want to talk to OLEDB drivers, some to ODBC drivers. If you're speaking of programming, in what? If it's something .NET then you don't want to use either, you want to use the .NET native provider from IBM. If you're using older COM based connections (VB6, Delphi, PB, etc.) then it almost doesn't matter. Code to ADO for data access and you can switch between the two in the connection string. I've seen some reports in the past that showed ODBC w/a slight advantage on first-connect and inserts and OLEDB w/an advantage on larger recordsets, but in general it's a wash. -Walden
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.