OK...enough of these misleading error messages! I have been struggling for almost a week on the problem of adding a reference to the file Mso9.dll. The file was originally located in the Program Files\Microsoft Office\Office folder. However, for reasons I won't get into, I copied this file to another directory.
This is where things get interesting. When I went to add a reference to the file located in the original location it worked fine. I then unchecked the reference and selected the other copy. What happens?
Can't add a reference to the specified file
This of course implies that this file can't be used by VBA. Say what?! I just used it while it was in another directory! So why can't it use it now? Nobody seems to know. It has NOTHING to do with what Microsoft states is the cause of this error message. I even built my own library (for something else) and successfully added a reference to it. However, once again when I copied it to another location and attempted to add it as a reference again (yes, I removed the previous one first) I get that same stupid message.
Does anybody know the REAL reason I am having problems? I would appreciate any help other than the direction Microsoft was pointing me to!
This is where things get interesting. When I went to add a reference to the file located in the original location it worked fine. I then unchecked the reference and selected the other copy. What happens?
Can't add a reference to the specified file
This of course implies that this file can't be used by VBA. Say what?! I just used it while it was in another directory! So why can't it use it now? Nobody seems to know. It has NOTHING to do with what Microsoft states is the cause of this error message. I even built my own library (for something else) and successfully added a reference to it. However, once again when I copied it to another location and attempted to add it as a reference again (yes, I removed the previous one first) I get that same stupid message.
Does anybody know the REAL reason I am having problems? I would appreciate any help other than the direction Microsoft was pointing me to!