We have one Vista laptop here which we get a bunch of "Could not load vba..." errors when we try to run Aecosim. Any ideas what could be causing this?
John K.
There was an ST in previous versions of building apps related to Microsoft Office (might also include MS Windows) security patches rendering MSVBA COM control inaccessible. It produced similar errors to what you've encountered, as well as errors utlizing specific VBA tools in ABD and other building products.
Not sure if it's related, but may be worth a try to implement.
"ST Description: user is unable to draw pipe/bar joist
Product:
Keyword:
Our V8i SELECTseries2 BIM applications were not tested with Office 2010
installed, so there may be an issue with how our VBA tools behave with this
combination. We are hoping to have this resolved in the upcoming AECOsim
Building Designer release, but in the interim it is recommended to use Office 2007
instead which has been fully tested against our applications.
Workaround:
Currently, Structural VBA macros throws VBA interface errors when ABD is
installed with MS Office 2010.
The workaround is to manually register MSCOMCTL.Ocx.
Win7 (32-bit):
"regsvr32 C:\Windows\System32\MSCOMCTL.OCX"
Win7 (64-bit):
"regsvr32 C:\Windows\SysWOW64\MSCOMCTL.OCX"
1. To register it right click that file and choose ‘open with’ ‘select
program from list’ click ‘browse’ and browse to the following file
C:\WINDOWS\system32\ and double click on the ‘regsvr32.exe’ file. You will
get a message that it was successfully registered.
Additionally there is Microsoft documentation and Fix it applet related.
http://support.microsoft.com/kb/2597986
Just a general question related to all that VBA stuff.
It seems that Bentley has a tremendous problem supporting all those different Office versions. The only supported version it seems is Office 2007, while testing with Office 2010 is going on at the moment. The version we have on our latest PC's is 2013.
As far as I know Microsoft wants to abandon VBA in its Office products and wants to move over to something more adapt. A step overdue, if you ask me.
That said, I wonder what the strategy for Bentley is regarding that.
FWIW, ABD has always fully supported Office 2010 - that's the combination I've been running for the last 1-1/2 years. Office 2013, however, is not yet tested nor certified.
While it would be wonderful to remove the VBA related code from ABD, it is a huge task to cover all the tools that currently use it - Structural assembly and translators, HVAC and plumbing tools, hooks into drawing rules, etc. I believe it's "on the list", but it will simply take time. The new Bar Joist and Deck tools on the Structural side are two examples of where we are now using non-VBA code.
Just curious - what are the alternatives?
Generative Components is more or less C#, isn't it?
Yes, it would most likely be a programming language like C++ or C# or whatever it is they use. That doesn't mean that functionality from other apps such as GC can't come into play in some cases, but probably not for the majority of the current VBA tools.
It seems that this error has revisted us again. We are now getting this error on a couple of our computers running Windows 7. Has anyone come across anything new about this error?