Reference settings attached to workbook or application or something else?

Hi,

In the VBA editor, Tools > References...

Are the checked available references attached to the workbook, to the instance of Excel, to the machine’s Excel settings, or do they depend on something else (such as the VBA code contained in the workbook's VBProject)?

If I perform the following experiment...
A) Open a workbook, enable/disable certain references, save and close the file, and close Excel.
B) Then open Excel again, open a different workbook, enable/disable a different set of references, save and close.
C) Then open the original workbook. Would I see the reference settings from A) or B)?

...I get different results for numerous different scenarios ran (for some experiments the references seemed to be attached to the machine's Excel settings, for others to the files...).

My end goal is to programmatically set a reference to be checked or not - depending on some argument. The easiest way, from my reading today, would be to ensure that in the base version the reference is always checked... and then programmatically uncheck it if the argument tells us to. (Versus programmatically adding a reference).

So I'd like a hard-and-fast rule that allows me to anticipate, without uncertainty, whether a particular reference will be checked for a certain file on a certain machine.

Thanks all,

Jim

Hi !

Instead of using an early binding (via activating any reference to the project)
why not using a late binding via the CreateObject statement ?

References are saved with the workbook.

I would suggest you to loop through references, and if the one is not checked, then add it via VBA. The reason is, when you will distribute the excel between different users the references can vary. But you have to also be aware in case users have different version of excel, so the libraries are different as well.