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 Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error: "Can't find project or library"

Status
Not open for further replies.

ssVBAdev

Programmer
May 23, 2003
257
US
I have an .xls file that many people in my company use without problem. But, I have recently overhauled the file and am now testing it on other machines. Here's the deal:

- I have Excel 2000, this particular user has Excel '97
- The previous "Version" of this .xls file worked fine on their computer.
- Now, with the new version, they are getting an error: Can't find project or library.

- working over the phone (they are in another location) I had the user send screen shots of the errors and the debugging screen... Here's the odd part...
The macros seem to be catching on simple functions such as "Left()" and "chr()"!?!? These are function I used in my previous "Version" without any problems.

Now, checking their machine for the Reference files, they don't have the files mso9.dll and excel9.dll (but I'm sure these are specific to XL2000(??)) and also does not have stdol2.tbl... all of which show as the "location" in the Tools-References dialog box in the VBA IDE.

-The user also does not have the VBA6 folder (at all) in the C:\Program Files\Common Files\Microsoft Shared\VBA\ path.

This is a little perplexing...
Any Thoughts...
 
I don't know about Excel, but in Access the symptoms are identical and the problem is that a reference is "MISSING:". Uncheck all MISSING references and (hopefully) find equivalent references that you can re-check. Sometimes you have references you don't even use, or added on a whim months ago ("What does that Macromedia Flash control do?") and forgot about.

You specifically mentioned Tools->References, but check it again--on the user's machine.
 
Well as it turns out it was a problem with the Commond Dialog Conrol again (comdlg32.ocx). I thought I had it fixed but apparently not. So, it's fixed. I just "Browsed" for the comdlg32.ocx file and all is right with the world again.
Thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top