CODEWITHSUNDEEP
oracle-databasevbaexcelms-officeoraoledb
Shekhar Nalawade
Shekhar Nalawade

Reputation: 127

error 3706 provider cannot be found. it may not be properly installed

All.

I have used a DLL approach explained on How to securely store Connection String details in VBA

This code is running very well on windows 10 64 bit and MS Office 64 bit. But same copy of the files i am not able to use on Wndows 8.1 Pro and MS Office 64 bit.

DLL generated is converted to host machnines environment by using 

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm c:\windows\syswow64\OraConnection.dll /tlb /codebase

But still same error i am facing. About environment variables care has been taken. My Connection string is 

"Provider=OraOLEDB.Oracle; Data Source = ;  User ID =; Password=";

Upvotes: 1

Views: 13617

Answers (2)

Shekhar Nalawade
Shekhar Nalawade

Reputation: 127

In the Succesfull machine i was using Release 12.2.0.1.0 for ODAC 12.2c Release 1 as oracle client.

But saw a latest version of the oracle client as 64-bit ODAC 12.2c Release 1 (12.2.0.1.0) for Windows x64 which was released on 1st June 2017.

Installed the same. And my error was resolved. When i observed system environment variables i saw few things added into it. E:\app\client\Admin\product\12.2.0\client_1;E:\app\client\Admin\product\12.2.0\client_1\bin;C:\Users\Admin\Oracle\;

I dont know actually what they did. But error was resolved.

Can anybody throw highlight on this?

Upvotes: 1

this
this

Reputation: 1426

I'm not sure what the DLL buys you beyond simple obfuscation. All you're doing is making it a bit harder to get to but not actually protecting the privacy of it in any meaningful sense. My normal advice for management of connection strings is to simply don't save user/password. Instead, require the users to input the username/password at runtime and ensure that you have Persist Security Info=false in your OLEDB connection. That way, once it's opened, the full connection string is now inaccessible and there's no reference to a password. That's much more secure than sticking it in a variable in a DLL and crossing your fingers nobody knows how to read a memory dump or attach a debugger.

That said, that's not germane to your question, not able to the use the provider. First thing I'd do is to rule out whether the DLL is causing a problem that you didn't expect by removing it and using the provider directly. If it likewise fails, then you know the DLL has nothing to do with it and you need to work out with Oracle's provider documentation to get to the bottom of the issue.

Upvotes: 0

Related Questions