Class does not support Automation or does not support expected interface.
I have a VB application that's hitting a SQL Server and some of my users are getting this error message. Does anyone have any idea why this is happening ?
Some DLL(s) may not be on the client PC, not registered(properly) on that machine, or have the wrong version.
[/b][/i][/u]*******************************************************
General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!
Well, if you can figure out where in the application this is happening, then you may be able to narrow it down.
It may be worth while to de-install the application and all of it's non-shared components, run a registry cleaner, then re-install the application.
But first, I would make sure the correct version of MDAC is installed. It may be an ADO component or a database driver.
If it uses JET, and MDAC 2.6 or higher was installed, then it may be also a good idea to install the latest service pack for JET as the JET Dll's are not delivered with this version of MDAC or higher anymore.
The same holds true for any other ODBC drivers. [/b][/i][/u]*******************************************************
General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.