Without knowing anything about the actual error message (please, provide it)
I can only guess: it's likely that you've got a broken reference in the
workbook.

I recommend that you work together with the user to establish what's going
wrong with your VBA code on their machine(s): enter the VBA project, and
check the references. What is the exact set of dependencies? Are all those
files really present on the target machine? Make sure that all those are
deployed together with your project.

Cheers,
/MP

"cheesey_toastie" wrote:

A long established spreadsheet is now loading the VB IDE for some
reason. As the project is password protected this causes the user to
have to enter the VBA password which is not ideal.

Anyone know why Excel does this?? I'm assuming its a bug, is there is
a workaround?

Steve