Runtime Error 3706: Provider Cannot be Found [Fix]

The runtime error 3706 occurs when users try to run some codes using VBA. This frustrating error can be due to minor issues with your code when referencing a provider.

If you are also dealing with this issue, this guide will show you how to fix it, just like we did with the runtime error 438.

Why am I getting the runtime error 3706?

The major cause of this error is if some of the details in your code are incorrect. An example is if you provided the wrong OLEDB version in your code.

So, majorly, this error is usually down to minor issues with your code and can be fixed by making the little changes required.

How can I fix the runtime error 3706?

1. Ensure the details are correct

The only solution to this issue is to make sure the details provided in your code are correct and updated.

For example, you might need to confirm the version of your MS Office on which the script is running if you are using the latest versions of Microsoft Office.

What’s more, you might need to change the OLEDB version from 12.0 to 16.0 if you are using the latest versions of Excel, like 2019.

Another thing to note is that you need to make sure your Version, driver type, and Extended Properties are correct. An example is the code shown in the image below that gave this error as reported by a user on Stack Overflow:

The solution to this was just to change the Version to 12, the driver to ACE from Jet, the Extended Properties to Excel 12.0, and some other minor changes made to the code, as shown below:

So, these little parameters are important to eliminate this runtime error 3706.

2. Use the latest version of Oracle

Sometimes, this runtime error 3706 can be due to an outdated Oracle client version. You need to check with your client to confirm the version and get the latest one available to prevent issues.

We can now conclude this guide on how to fix this runtime error for good on VBA. This issue is majorly down to minor issues with the details provided in your code.

Correcting these details accordingly should solve this effortlessly. If you are dealing with another issue like runtime error 3709, check our detailed guide to fix it.

Feel free to let us know in the comments below if you could solve this problem.