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. 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.

Db: 4.44:installation Error Office For Mac Download

No reboot required. 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. 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.

Killall cfprefsd - to kill cached preferences After above steps, just launch the Outlook application and you should be all set. Just don’t import anything from Mac 2011 installs. This issue doesn’t impact old Outlook 2011 application – it works without issue. Where is my Database File for Outlook 2011 and 2016? The Outlook database is completely separate from the one used in Outlook 2011. Outlook 2011 uses /Documents/Microsoft User Data/Office 2011 Identities Outlook 2016 uses /Library/Group Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/Main Profile Enjoy New Office.

Db: 4.44:installation Error Office For Mac Os

So far it’s all good.