OP, VBA in Office 2016 is not fully implemented yet, and VBA needs to be 'activated' in each app it's used in; 'activation', in my words, means that MS has provided Resource files in the Word app in the language and my installations of Office 2016 do have Russian Language Resources in the VB engine - whether this has been enabled by MS is another matter. VB in existing documents did not work for me until I enabled the Developer Tab, which is hidden by default. For instance (using English to describe the following, as it's my main spoken language), in Word's Preferences Pane choose the 'View' option (second from the left in the top row) and then enable/check the 'Developer Tab' (second from the bottom in the View Preference Pane) and close the Word Preference Pane. Choosing the Developer Tab reveals VB options. I've performed some simple programming in the interface and it works as expected; I am not investing much time in Office 2016 as it's a preview, but I can offer that VBA is working on the 3 Macs I've installed it on. OP, VBA in Office 2016 is not fully implemented yet, and VBA needs to be 'activated' in each app it's used in; 'activation', in my words, means that MS has provided Resource files in the Word app in the language and my installations of Office 2016 do have Russian Language Resources in the VB engine - whether this has been enabled by MS is another matter.

VB in existing documents did not work for me until I enabled the Developer Tab, which is hidden by default. For instance (using English to describe the following, as it's my main spoken language), in Word's Preferences Pane choose the 'View' option (second from the left in the top row) and then enable/check the 'Developer Tab' (second from the bottom in the View Preference Pane) and close the Word Preference Pane. Choosing the Developer Tab reveals VB options.

I've performed some simple programming in the interface and it works as expected; I am not investing much time in Office 2016 as it's a preview, but I can offer that VBA is working on the 3 Macs I've installed it on. Click to expand.The only remaining suggestion I have just to check the name of your hard drive in the name of any and all folders leading into the path of your files. Microsoft's Applications prohibit the use of certain characters in filenames, especially those that are referenced. Use Microsoft's Help to help you determine which offending characters are in the files path and/or filename. Also, if any of the offending/illegal characters are referenced in a visual basic macro, then you'll get error messages. In the visual basic macro, basically, you're debugging the code.

Old version of firefox for os 10.8.5? Firefox support has ended for Mac OS X 10.6, 10.7 and 10.8; Old versions of Websense cause startup crashes in Firefox. Vlc for mac os x.

If the trash can won't let you delete a file due to errors, make sure to restart and then wipe it (I had to do this for 'Powerpoint & Word are still in use' and for 'Arial, etc. Fonts still in use'). 3) Uninstall the program that is having issues (Endnote in this case). Home / Assistive Software / Texthelp Read&Write / “Can’t Load Visual Basic for Applications” when launching Read and Write Gold for Mac. Launching Read and Write Gold and Microsoft Office word produces the following error. “Make sure Visual Basic for Mac is installed on your computer. I just migrated all my data and settings from my old mac to a new mac book pro using migration assistant. Every time I open word 2011 I get the message Cant load Visaul Basic for Applications. Microsoft on Tuesday announced it would restore support for Visual Basic for Applications (VBA) to Microsoft Office for Mac, a direct result of complaints from users about the removal of the suite.

In Finder, you're basically adhering to Microsoft's requirements for filenames. Post Merged, Mar 11, 2016 --- This solved the problem for me in Office 2011. Delete the linkCreation.dotm file located here: ~/Applications/Microsoft Office 2011/Office/Startup/Word/linkCreation.dotm The file can somehow re-create itself (rarely, only happened once since I figured this out about a month ago), sometimes after opening word docs from other users, and/or when Office pushes through updates.

This causes the error message again -- just go back and delete linkCreation.dotm and you should be good again. Note: Unchecking the box next to linkCreation.dotm in the file menu Templates and Add-ins under Global templates and add-ins will not fix this. You must delete the file as indicated above. Initially I first deleted the normal.dotm file before deleting linkCreation.dotm, then rebooted.

That fixed also, but I've found that simply deleting linkCreation.dotm does the trick. No reboot required. Post Merged, Mar 11, 2016 --- This solved the problem for me in Office 2011. Malwarebytes for mac old version.