Microsoft Office Visual Basic issue after upgrade to MacBook Pro via Migration Assistant

I had similar problems recently with Office 2011.

I got in touch with MS, and after some serious grief from them, including a request for $90 to pay for their advice, a technician did solve the problem. It was a long process of trashing preferences etc. which I had no interest in remembering.

Here's the link to MS support:

https://support.microsoft.com/oas/default.aspx?&c1=505&gprid=15627&&st=1&wfxredi rect=1&sd=gn

Just struggled through this one for a while. I updated Office, then replaced prefs in both ~/Documents/Microsoft User Data and ~/Library/Preferences/Microsoft. No effect.

In the end, here's what worked:

• Locate com.microsoft.Word.plist in ~/Library/Preferences
• Find an earlier version of this file in Time Machine (before the odd VB dialogs started appearing).
• Restore.

If you don't have a clean backup, it would probably work to trash the file and start over, but I wanted to keep my preferences.

It worked fine in my case, thanks!

I'm having this problem, but the com.microsoft.Word.plist file doesn't exist either on my Mac or in any of my Time Machine backups . . ..

Tried a custom re-install of Office for just Visual Basic and that didn't work. Had to do a full reinstall of Office 2011, which wasn't nearly as painfull as I thought, and all my prefs are in tact.

I had the same problem after Migration Assistant. Verify/Repair Disk Permissions did no good. What worked for me (from another forum): start up Endnote then Customize > Deinstall. (This program creates references while you type in Microsoft Word.) After doing so, Word started up without complaint.

Mmm - just found this problem too.

Migrated to new machine OK, (a 2010 Macpro Mtn Lion), but although Excel & Word seemed to work normally, Visual basic give me the "Can't load Visual basic For Applications" error message.

Tried a custom install for VBA only - and wheheee - it worked. Ran my macro, which then froze Excell and had to force quit Excel. Tried the VBA editor to look for any errors, but just received the error message again. Rats.

Tried some of the suggestions above - trashing preferences etc - but no effect.

Saw another suggestion to change the name of the hard drive name back to its original name, and now it seems to work OK.

You cant make this stuff up sometimes.

This worked perfectly for me - same situation (used migration assistant to move apps to new mac). Did you encounter problems when re-installing EndNote? Or did you just stay away from it after this...

Thanks so much!

I was having the same problem on my macbook air - for similar reasons (migrating from one mac to another). For a while it would work ok if I just clicked "ok" on the screen with the error message (saw the screen twice, clicked ok twice each time!) that appeared when starting Word. Then - after a system upgrade I think - it crashed Word at startup and I had to force quit to get out. Happily problem is now solved - upgraded to Endnote X6. However, you have to make sure you uninstall and then trash earlier versions of Endnote.

Used Mavericks migration asstant to move to a new MacBook Pro 7 days ago and Word became unusable with Dragon Dictate for Mac with the 'Can't load Visual Basic for Applications' message.

After talking to the nice people at Apple support, they suggested calling the Microsoft Mac team- who wanted £65 to talk to me. Decided, with Pages installed, that Word wasn't worth the money to me, so politely declined and went back to the forums and worked through the suggestions to delete the preferences, run the updates again, using Font book to repair fonts & co

Tried the 'rename the HD to the same as the original' suggestion without sucess-

The only thing that worked for me was to reinstall Office from the disk image. Painless -- and the reinstalation preserved my registration and templates. Only problem was locating my copy of the disk image!

Same problem. I had Endnote X6 and X7 installed. What worked for me was to uninstall X6 only. (Customize-->Uninstall)

Worked for me, too. Something with Endnote 7 on OsX

same issue here. deinstalled endnote x7 & it fixed the problem - but now not sure what to do about endnote???? did you put it back on? and if so, how?

thx!

aleca

I used Migration Assistant to move from Yosemite on my 2011 MacBook Pro to my 2014 MacBook Pro, and this happened to me. I have EndNote X6 installed, and I was able to fix it without removing EndNote entirely.

Start EndNote X6

Open Customizer on the EndNote X6 menu

UNCHECK the "Cite While You Write" option (this is the option that installs the problematic code in Word).

Click Next (rather than Uninstall)

Click Next again (even though their window says that they'll be installing the feature, it actually removes it from Word.

Click Done.

Now you can exit EndNote X6 (or not) and start Word (I have Word 2011), and it works fine. No more VBA error that makes it unusable.

The EndNote suggestion worked the first time for me. Thanks