I just had this problem on a windows service app. Solved it by adding a reference to adodb. Didn't need it when testing on my own development machine, but the problem became apparent when I deployed to the target server. The reference includes the dll in the installation kit.
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.