How to Recognize unnecessary reference files in the vbe

**Wizz** · 06-18-2009, 07:00 AM

Hi,
I made an excell document with many many vba codes/procedures. While creating it, I was doing some tests/playing with the references in the visual Basic Editor.
My problem is now I dont know which ones are necessary and which dont. I want to remove any unnecesarry reference. How can I know which ones are necessary for my project to run properly and which dont??

I appreciate very much your help.

**romperstomper** · 06-18-2009, 07:06 AM

Try unchecking them (apart from the first 5 if you have any forms) then compiling the project each time (Debug-Compile). If you get errors, you need the reference. (some you may not even be able to uncheck).

**Wizz** · 06-18-2009, 09:18 AM

Nnice one !!
That option looks very interesting. I've been checking Excel's help and the web, but couldnt find more info on what and how much does that function does.
Do you have any source were I could read/learn more about the compiler??

Thank you very much.

**romperstomper** · 06-18-2009, 09:29 AM

The compiler doesn't effectively do much more than a syntax check in reality (VBA is not a truly compiled language)

**Wizz** · 06-18-2009, 09:49 AM

My interest in learning more is because:

1- I deliberately misspelt "EnableEvents" ("EnnnableEeevents") and then run the Compiler. It found no error.

2- While removing and compiling, in some cases, there was a bar wich counted the percentage compiled (very fast). But in some cases, nothing happened (after I pressed compile every option in the debug/compile menu was grey). When I removed another reference, it was black again.

3- I was able to remove almos every reference but 4. From those, 3 reference I could not even uncheck, and the 4th showed me an error while definig a variable (Dim SelectMenu As FileDialog)

4- When it finishes compiling, does it send a message or I just have to asume it finish compiling?

Thanks a million romperstomper

**romperstomper** · 06-18-2009, 09:55 AM

1. You should use Option Explicit which forces you to declare all variables (you can set this under Tools Options in the VBEditor). Otherwise the compiler would assume that your misspelled EnnnableEeevents was an undeclared variable. (though if you had used Application.EnnnableEeevents it wouldn't be an issue)
2. That just means it was too fast!
3. That was the point of the exercise.

4. No, no message unless it finds an error.