runtime error 5981 (97 SR-1)

Topic

New Reply

I m getting an error message: runtime error 5981. Could not open macro storage. Doc does contain macros from a known/trusted source. The only thing I could find in the MS KB said to remane normal.dot, and try opening the file again. No luck. Any help would be appreciated…Neil

Reply | Quote

Replies

Another thing to try is to re-install VBE.DLL. You need to have your Office 97 CD-ROM available for this. See the third method in OFF97: Errors Starting Visual Basic Editor.

You can also try the steps outlined in Systematic Approach to Behavioral Problems in Word (97/2000).

Reply | Quote

Another thing to try is to re-install VBE.DLL. You need to have your Office 97 CD-ROM available for this. See the third method in OFF97: Errors Starting Visual Basic Editor.

You can also try the steps outlined in Systematic Approach to Behavioral Problems in Word (97/2000).

Reply | Quote

Another thing that can cause this error: When one sets up a VBA project in a document or template, it will automatically refer to certain external files that come with MS Office. However, the programmer can add references to other files, for example, a file that stores controls (like a drop-down calendar that lets you pick dates) or a file that contains functions for working with database files. If a referenced file does not exist on your computer, then you can get this (unhelpful) error. If no other technique works to open this file, ask the sender to remove all references other than the standard ones (Office, Word, VBA, and OLE) and see if that helps.

Reply | Quote

Another thing that can cause this error: When one sets up a VBA project in a document or template, it will automatically refer to certain external files that come with MS Office. However, the programmer can add references to other files, for example, a file that stores controls (like a drop-down calendar that lets you pick dates) or a file that contains functions for working with database files. If a referenced file does not exist on your computer, then you can get this (unhelpful) error. If no other technique works to open this file, ask the sender to remove all references other than the standard ones (Office, Word, VBA, and OLE) and see if that helps.

Reply | Quote

I encountered the same error when opening a file with a (ore more) Sub/Function with the same name as a Sub/Function in a add-in. Temporarily de-installing the add-in and renaming the offending Sub/Function cured the problem.

Jan

Reply | Quote

I encountered the same error when opening a file with a (ore more) Sub/Function with the same name as a Sub/Function in a add-in. Temporarily de-installing the add-in and renaming the offending Sub/Function cured the problem.

Jan

Reply | Quote