My company switched my pc from Windows 2000 to Windows XP Pro and
installed a new version of Office. My old version was 2000 and now I
have 2003 or XP(Im not sure since it doesnt say). The version number
of office Excel is (11.8146.8132) SP2.

After this change I have been getting the error on this one project
that used to ALWAYS work with my old pc and version of Excel. The
error I get is:
"Compile error: Cant find project or library"

Then when I click ok, it highlights the following code in my project:
"Function CompTypeToName(vbcomp As VBComponent) As String"

This code came from Chip Pearson and the library needed is "Microsoft
Visual Basic for Applications Extensibilty 5.3"

Problem is - I have this library highlighted and still get the error.

I have had similar problems in other projects that use different
libraries, but have managed to fix them by removing the reference to
the "problem library" and then putting it back. After that my project
would always work. Im not sure if this is a glitch or installation
issue. Anyway that worked on my other projects but will NOT work to
fix this project that uses "Microsoft Visual Basic for Applications
Extensibilty 5.3".

I even removed the reference to "Microsoft Visual Basic for
Applications Extensibilty 5.3" saved the project, exited Excel,
restarted Excel, opened my project added it back, and still got the
same error.

Then I tried to download the example book from Chip Pearson's website,
I even got the error with that workbook. I verified that "Microsoft
Visual Basic for Applications Extensibilty 5.3" was checked.

I also checked in my "C:\Program Files\Common Files\Microsoft Shared
\VBA\VBA6" program directory and browsed for the "VBE6EXT.OLB" and set
the reference that way. That still didnt work.

Just in case this is important, the files located in this directory
a
apc64.dll (version 6.4.98.91)
VBACV10.DLL (version 2.0.0.7411)
VBACV10D.DLL (version 2.0.0.7411)
VBACV20.DLL (version 2.0.0.6712)
VBE6.DLL (version 6.4.99.72)
VBE6EXT.OLB (version 6.0.99.71)

I have even restarted and still get the same error.

I just dont know why I cant get this to work. Could it be a policy of
some sort? Any suggestions?



Thanks
Todd