Results 1 to 3 of 3
  1. #1
    Join Date
    Oct 2001
    Thanked 0 Times in 0 Posts

    Macro storage error (Word 97 SR2, NT 4)

    On SOME PCs trying to open theVB editor (in Word 97 only i.e. Excel 97 OK ) launches a dialog box with the error "Could not open macro storage". Once in the VBE you do not see a reference for "Document 1", or any other for that matter, just NORMAL.
    The error dialog only opens when you try to go into the VBE or you try to run a file with contained macros - which is pro0blem if your are trying to deploy a template with macros.
    Current desktop environment is NT 4 under Novell Netware 5 if thats relevant.
    Anyone struck this before?

    any feedback appreciated.


  2. #2
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Silicon Valley, USA
    Thanked 94 Times in 90 Posts

    Re: Macro storage error (Word 97 SR2, NT 4)

    I get this error when running a macro that makes reference to a DLL or type library that does not exist on the new machine. I'm not sure whether this applies to your situation, but in the VB editor, you could open Tools, References and look for one that says MISSING or something to that effect. You might also need to repair some VBE files.

  3. #3
    Bronze Lounger
    Join Date
    Jan 2001
    Melbourne, Australia
    Thanked 0 Times in 0 Posts

    Re: Macro storage error (Word 97 SR2, NT 4)

    On the users pcs - with the error message appearing
    the users have the wrong version of a visual basic editor dll.
    We were getting this error message the other day when we were setting up a brand new laptop(latest model dell) for user.

    to resolve:
    1.Open up word/excel -applicaiton
    2. run code - error message will appear.
    ( this will create a temp folder file VBEmsforms.exd
    note the location.
    3. exit out of application
    4. do a search for file mxforms so you know location
    5. on a pc thats working copy the file msforms.exd to users pc not working
    to the temp location eg C:TempVBEmsforms.exd
    6. start application again & run code - this should work.

    Microsoft Knowledge base - Q162053;en-us;Q162053

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts