My client is getting the error message "Could not open macro storage" when they try to run any macro in my template. They have tested it on multiple computers, so it isn't one of the usual problems (lack of memory, corrupt Normal.dot or corrupt VB DLL). Everything runs fine on my machine.
Isn't it also possible to get this message if you have a reference in the template to a component that the user doesn't have? At one point while working on the template I played with the references in the VB Editor. I thought I turned everything back the way it was. Could this be the problem? How do I make sure I've gotten rid of those references?