Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error in loading DLL

Status
Not open for further replies.

belden

IS-IT--Management
May 9, 2002
9
US
I've had an Access application working for about 2 years, until this morning! Now I get "Compile error: Error in loading DLL" when I try to run it.

I should preface this by saying I'm tech savvy, but know next to nothing about VB.

Nothing changed. I think.

The only thing that might have changed is that I was working on another Access db project that I was trying to get some borrowed VB work in. While I was trying to get it to work I was monkeying with the Reference Libraries because some comments made in another thread made me believe I needed DAO instead of ADO.

By changing reference libraries in one Access db did I hork up the other Access db?

Thanks!

Belden
 
Changing from DAO to ADO isn't as changing the references
I'd change the references back to what they where. If the 2 projects are linked they yes it could have messed up the other. But error loading DLL sounds like something isn't set up right rather than a reference problem. Changing the reference would give you an error like unexpected interface or something like that normally
 
SemperFiDownUnda,

Thanks for the input.

Yeah, it does sound like something isn't set up right, but it had been working fine Friday morning.

Could the DLL(s) have gotten corrupted or something, or moved somehow? Where are they normally located?

Just to clarify, what I mean by reference library is when you go to Tools and References and add or change the "references" like the Microsoft ActiveX Data Objects 2.1 Library.

oi, I feel like an idiot because I don't necessarily know how to communicate some of this stuff.

Thanks,

Belden
 
Belden: Did you ever resolve this problem. I am encountering exactly what you encountered.
 
evalesthy,

Sorry, I never found a solution to the issue. I undid what I was doing and made sure the reference libraries were back to what they were when I started with the other project. Fortunately for me, I didn't really need the project that caused the error.

I wish I could be of more help, but like I stated in my earlier posts I don't know much of VB.

Good luck,

Belden
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top