Challenge?

[dsc]

I think this may be a tough one.

I was altering a macro that opens an Access database and works with it.
Something caused the computer to freeze. I had to do a power-off.

When I restarted the computer and opened word, I could no longer run that
macro or edit macros. I have a toolbar icon for the macro. When I click on
it, Word crashes. When I go to tools->macros->edit, Word crashes. When I go
to tools->macros->Visual Basic Editor, Word crashes. I can't get into the
Visual Basic Editor no how no way. Trying makes Word crash.

Here's what I've tried:

Uninstall and reinstall of Microsoft Office.
Delete all temp files.
Delete all dot files.
Set Pagefile.sys to size zero.
Use Norton Utilities Disk Doctor to look for crosslinked files, etc.
(nothing found)

Even with a brand-new clean install of Word and a brand-new clean
normal.dot, when I go to tools->macros->edit, Word crashes. When I go to
tools->macros->Visual Basic Editor, Word crashes.

Our office IT guy (who may be a theta geek but is definitely not an alpha
geek) wants to reformat the hard disk and reinstall everything. I'd rather
open my veins. I've been tweaking that computer to suit myself for two years
now, and I don't want to lose all that.

Anybody ever heard of this?

Any guesses?

All assistance gratefully accepted.

 

[Chad DeMeyer]

Was the macro stored in Normal.dot? If so, that's a bad place to store
macros - Normal.dot seems to be especially vulnerable to corruption. Try
renaming Normal.dot to Normal.old and restart Word to let it create a new
Normal.dot. See if that fixes your problem. If it does, you can copy
customizations from the old Normal to the new using Organizer. Move the
macros to a global add-in template.

Regards,
Chad

 

[dsc]

Thanks. I did that, and it didn't fix the problem.

What else do you think it could be?

 

[Gene]

After Uninstalling MS Office, access the Registry and delete remaining
Office Registry Key Settings. Reboot and reinstall.

-Gene

 

[dsc]

Thanks.

Unfortunately, time constraints and mediocrity conspired against me. The IT
guy reformated the hard drive and reinstalled.

 

[MK]

I had the same problem, mine was a corrupted reference to
a custom dll. Try to open the template the macro is
contained in on another machine, remove all references and
save it then try to open it on your machine again and
recheck the references. If that doesnt work, export all
neccessary code from the macro on the other machine and
startup with an old version on your machine, then just
replace the old code with the new.