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 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...