Share via

Excel VBA "Compile error: Can't find project or library" [but no references are MISSING]

Anonymous
2017-02-14T20:30:22+00:00

My daughter is having a problem with an Excel macro workbook that she has taken over.  She modified the spreadsheet and only the text of a button within the macro code.

A user is getting VBA "Compile error: Can't find project or library" error on the spreadsheet that works fine on my daughter's laptop.

We have checked for MISSING references but not found any on the user's pc.  The user now has the same references checked as does my daughter.

The user was and still is able to run an earlier version of the workbook.

My daughter ran into a similar issue 2 years ago and found the workaround of saving the file in an Excel 97-2003 format to enable another person to use the workbook. However, that won't work in this case because she now gets a warning about significant loss of functionality.

My daughter has Excel 2016 and the user with problems has 2010.

Any help will be greatly appreciated.

MORE INFO:

My daughter has found another PC, running an older version of Excel, which can run the previous version of the workbook but not the newer version.

Microsoft 365 and Office | Excel | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
  1. Anonymous
    2017-03-01T15:41:58+00:00

    Yes in case you're referring to external Office libraries AND are using different Office versions, late binding is the way to go indeed.

    1 person found this answer helpful.
    0 comments

7 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-02-23T19:16:47+00:00

    Thanks! I'll send this information to my daughter now.

    0 comments
  2. Anonymous
    2017-03-01T14:27:17+00:00

    My daughter got to the point where the software was going to check whether she had the updates, but she couldn't tell whether it would do the updates without giving her an op to say no.

    But actually it turns out the the issue may be caused by references.  The macro uses Outlook and when Excel 2016 is used to make any changes to the excel file the reference to Outlook is set to 2016.  If she then goes in and changes the reference to an earlier Outlook, then the macro will work under Excel 2010.  This process is getting her through a busy time, but she knows that "late binding" is probably a better and easier long time solution.

    With many thanks to you (Jan Karel) and OssieMac, I am marking this closed.

    but I can't see how to mark it closed?

    0 comments
  3. Anonymous
    2017-03-01T16:24:19+00:00

    THANK YOU VERY MUCH!

    0 comments