Updated April 2017:
In some situations a series of VBA errors can occur when starting AECOsim Building Designer. Two possible causes are:
In the second case we have a number of support articles detailing the actions to take to resolve these problems.
However before delving into these solutions an easier option is (assuming it is installed, and it needs to be to take advantage of the DataGroup 'Edit in Excel' feature) to run a repair installation on Microsoft Office. This very often resets the VB/VBA components to the required state.
For background information and full details read Microsoft Security Bulletin MS12-027 disables VBA Scripts (updated 04-20-2012)
To resolve this run Microsoft Fix it 50864
For background information and full details read Microsoft Security Bulletin MS12-060 (update to MS12-027) disables VBA Scripts (released 08-14-2012)
To resolve this for Windows 8 based systems run Microsoft Fix it 20097
To resolve this for Windows 7 or earlier based systems run Microsoft Fix it 50930
[Note the Microsoft 'Fix It' links are correct at time of writing but are external links so may change]
Microsoft's April Security Updates Kill VBA Scripts
VBA errors when using certain Structural or Mechanical tools
Class Factory VBA error opening AECOsim
VBA Error - Class not registered deals with unregisterd fm20.dll module (added April 2017)
I've created a service request to follow up on your question.
I run into 4 of these messages when I start AECOsim Building Designer. The project configuration(s) should not be a problem as this also happens when I use the pre-packaged ones (ie the examples). Also our company-wide configurations work well on Windows 7 machines. This is one of the first two Windows 10 machines that get Bentley software at all. Bare Microstation that is used by Speedikon does not have these issues.
Registering fm20.dll did not work out. Ah, the office package installed is by Microsoft and Version 2016
If it is related to an installation/upgrade/downgrade of Microsoft Office, it may be that FM20.dll is not in the registry. In my situation the file was intact and just needed to be registered. I have 64-bit architecture. I ran cmd.exe in administrator mode and executed:
for 32-bit I think it would be
This worked for me but I'd exercise caution when dealing with the Registry.
Hi Tim, if the suggestion I made in response to your SR works I'll add it to this item.
None of these fixes sort my VBA issues. have tried all fixes suggested above and all attached threads.
I have 'repaired' Office
I have repaired AECOsim
I have reinstalled AECOsim.
I have downloaded and run the AECOsim prerequisites installer...
I still get 14 errors on open and 14 on close...