This content has been marked as final. Show 7 replies
I've never tried it, but here's a download page with the instant client and an add-on package for it that enables ODBC. http://www.oracle.com/technetwork/topics/winsoft-085727.html You might want to try those.
I know that the full ODAC installation works, but that requires doing the client install.
Hi, thanks for your response but for that I need to run a executable to install the odbc on the client and I don't want that.
Any other idea?
For ODBC? Not really. It requires registry changes in order to register an ODBC driver with Windows and there's just no getting around that.
If you were to write something that made all those changes yourself, then you might be able to get around it by having your app's installer do it, but that would be highly error prone.
If you were using .net, you could use the managed provider that's coming out soon.
I'm using VB.NET because my application has been migrated from VB6 and it is very big.
What would be the best connection type to use without having to make big code changes and with a minimum risk?
That's going to depend on how the code is set up now, honestly and is beyond my ability to answer accurately.
That said, if you're using ADO.net already for your data access and simply using an ODBC connection in your connection string, changing to the ODP.net managed driver (once available) and switching your connection string to an ODP.net one shouldn't be very painful.
I'm using ADODB, not ADO.net so it's not an easy conversion but thanks anyway.
Then you're probably stuck doing the installation. That's just part of how ODBC works in Windows, unfortunately.