Tools/References stopped working in VB editor (Word 97)

Topic

New Reply

Suddenly I can’t access any of my Word VBA project references. When I open a Word template, go to the VBE, and click Tools, References, I get the error message “Object library not registered.”

I’ve tried everything from deleting the VBA.ini file to trying to register various VBA dll’s to re-installing Word and VB 6.0. I’ve never had this problem in several months of working on this pc (which runs Win 98). Nor have I installed any new programs in that time.

Can anyone offer any resolution? Thanks.

Reply | Quote

Replies

Does the dialog open after that or does it just refuse to open? If it won’t open, perhaps it would be possible to run some VBA code to see what the references are supposed to be so that the missing one can be identified. Note that this dialog reads the Registry, so if you have done any registry “clean-up,” you might scan the log files that typically creates to see if something important was deleted.

Reply | Quote

Thanks for the suggestions.

The dialog refuses to open.

I did run regcleaner yesterday. I merged back the Undo reg file; no change.

I suppose I could run some VBA code to check the references, but I’d have to write the code in Excel or someplace, and automate Word from there. I can’t put the code in any of my Word templates, because I can’t set a reference to the VB Extensibility library…

Reply | Quote

Try this little diagnostic document.

Reply | Quote

Thanks. Your code didn’t run – it crashed on the variable declaration for the VB Project.

But that got me looking at the VB extensibility library. My pc had the old (5.0) library, vbeext1.olb, in program filescommon filesmicrosoft sharedvba. Other pc’s that didn’t have the problem had the newer library, vbe6ext.olb, in program filescommon filesmicrosoft sharedvbavba6.

I installed Access 2K just to get the VBA6 libraries, then uninstalled it. Problem solved!

Thanks for the helpful suggestions and code.

Bob

Reply | Quote

That doesn’t make a lot of sense because Office 97 was based on VB5, not VB6, so it shouldn’t use the VB6 library anyhow.

Reply | Quote

You’re absolutely right – it doesn’t make sense. But that’s what happened.

Reply | Quote