Well, like I said, when I ran your "Word Check if Open" VI, I did not get an error, so the problem, as far as I can tell, isn't with the VI, but with the computer you're running it on. One thing I noticed is that when I opened the VI it showed as having been changed. The change was that an external interface was changed, meaning that it had to resync with the version of Word that I had installed on my computer, which is probable different than the one you have. The "Class not registered" is a pretty generic error, and is usually pretty hard to track down. A few things to try:
- If you're not logged in as Administrator, log in as Administrator and see if that makes a difference. Could be a permissions problem.
- Take a look at the document "How Do I Manually Register Type Libraries, ActiveX Controls, and ActiveX Servers?". Word is an ActiveX Server.
- See if the same thing happens on another computer, or better yet, on another computer running a different version of Word.
- See if the same thing happens when you try to instantiate the ActiveX interface using something like VB.
Sorry I couldn't be of much help on this one.
Regarding your question on global reference: that term is pretty meaningless without a context. Usually it's a reference that you keep in a global variable that you access within an application. Or, are you referring to the "Global" object that you're using in the VI? In that case, the "Global" object is just a shortcut. From the Office Visual Basic Reference:
Global Object
Contains top-level properties and methods that don't need to be preceded by
the Application property. For example, the following two
statements have the same result.
Documents(1).Content.Bold = True
Application.Documents(1).Content.Bold = True