Can't Find Project or Library; also can't access VBA Codes or "References"

[jewkes6000]

I have a .xlsm file with a ton of macros. One of my co-workers was using it and suddenly started getting the "Can't Find Project or Library" error. I've researched on the internet and a common solution is to go into the VB editor and check the references; however, I can't even access the reference box. Whenever I open the VB Editor (Alt+F11), I can do anything in the editor. I can select "Tool" then "References"; however, nothing happens when I click it. Further, when I open up a module, I can't see my code. I've attached a screenshot of what this looks like. It's just a blank screen.

A couple things to note:
- It only happens with this Excel file. Other macro enabled files work fine
- With this file, we gate the same issue on both mine and my co-workers computer.
- I've also tried registering a library file by using the run command as explained in the link below, but that didn't work either.

Can't Miss! How to Fix Can't Find Project or Library Error?

When your Excel files can't find project or library error, you can get the solution from this page to fix it.

recoverit.wondershare.com

- When I click on a UserForm in the VB Editor, I get an error which says "Module not found" (see 2nd screenshot below)

Any suggestions or help is much appreciated.

Thank you.

 

[gplhl]

I suffer from this and am convinced its network related causing the problem. However, my boss came up with a fantastic solution that works a charm. We have a back up file, however this does not have up to date information in it. To overcome the problem, he found that opening the backup and the file with the issue in 7-Zip, navigate to the "xl" sub folder and replace the vbaProject.bin file with the one from a working backup. Works a charm and literally takes seconds with a drag and drop. Only caveat is that you need a backup with an uncorrupted version of the vbaProject.bin

 

[zumbaZumba]

I suffer from this and am convinced its network related causing the problem. However, my boss came up with a fantastic solution that works a charm. We have a back up file, however this does not have up to date information in it. To overcome the problem, he found that opening the backup and the file with the issue in 7-Zip, navigate to the "xl" sub folder and replace the vbaProject.bin file with the one from a working backup. Works a charm and literally takes seconds with a drag and drop. Only caveat is that you need a backup with an uncorrupted version of the vbaProject.bin

I only registered to thank you man! Other solutions mentioned here failed me, but yours worked a charm, saving a lot of work. Thanks again !

 

[AmyK023]

I suffer from this and am convinced its network related causing the problem. However, my boss came up with a fantastic solution that works a charm. We have a back up file, however this does not have up to date information in it. To overcome the problem, he found that opening the backup and the file with the issue in 7-Zip, navigate to the "xl" sub folder and replace the vbaProject.bin file with the one from a working backup. Works a charm and literally takes seconds with a drag and drop. Only caveat is that you need a backup with an uncorrupted version of the vbaProject.bin

This solution worked for me as well. THANK YOU.

I'd like to add that I, too, believe the cause to be network-related. I've found that if I open a macro-enabled workbook or a workbook linked to the macro-enabled workbook from a VPN-only accessible location and do not save and close the workbook before the VPN disconnects, I get this corruption.