Hi everyone, I am currently trying to adjust a mvba that worked for V8i and make it usable in Microstation Connect. I understand that Microstation Connect is a 64 bit application and from the following post I understood that I need to activate the "Microstation ActiveX Data Objects 6.1 Library in the References. I could also find the following file C:\Program Files\Common Files\System\ado\msado15.dll file. Aftering activating that, when I clicked on the button that refers to the mvba then the following error pops up:
C:\Program Files\Common Files\System\ado\msado15.dll
It can be roughly translated to : AxtiveX can't create an object
When I go to the error, the following is highlighted in yellow.
I probably need to change something in here, but I am not sure what. Does anyone might have an idea into what I need to change the highlighted lines?I get the feeling that this is not necessarily a Microstation problem, so maybe I should ask the question also somewhere else.
Joy van Vliet said:that I need to activate the "Microstation ActiveX Data Objects 6.1 Library in the References.
What libraries were referenced in V8i version? It is the place where you should start: When anything worked in V8i, exactly the same library, but 64bit version, should be found.
Joy van Vliet said:Aftering activating that
It is not "activating", but "referencing", which means MVBA knows the specific project accesses particular external library.
Regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi Joy,
What version of Excel are you using?
If you can't solve the problem, would changing your Macro to connect to MicroStation from Excel perhaps eliminate the issue?
I have the following version
You mean to connect to Microstation from excel (the other way around)?
Joy van Vliet said: I am currently trying to adjust a mvba that worked for V8i and make it usable in Microstation Connect
Please read this article. Make a note of Bitness: 64-bit or 32-bit, and review the version of your installation of Excel.
Joy van Vliet said:when I clicked on the button that refers to the mvba then the following error pops up
You have the wrong installation (32-bit) of Excel. Consult with your IT department and ask them to install 64-bit Excel.
Regards, Jon Summers LA Solutions
Yes, exactly that. Obviously you've not given any details on what your Macro does, but if the Macro was instead written to suit Excel as the host application, I'm wondering if creating an instance of MicroStation to open a drawing could be an option that might alleviate your issue? I do the same for reading & updating title block tag values and it makes more sense (to me at least) that any Macro involving Excel and MicroStation, be written in Excel.
Jon Summers said:You have the wrong installation (32-bit) of Excel. Consult with your IT department and ask them to install 64-bit Excel.
As I remember I had similar bitness issues in a thread last year, that was one of my initial thoughts, however I couldn't determine if that build was 32 or 64bit.
However, its worth noting that I have no problems whatsoever using creating an instance of 32-bit V8i SS10 from 64-bit Excel VBA IDE for Tag value reading and writing, so perhaps bitness isn't the issue after all?
Barry Lothian said:I couldn't determine if that build was 32 or 64bit
Find the backstage Help menu...
Or, for example, SigmaZone.
Oh I know how to find out the bitness version of Office, I meant I cannot tell from the build number shown in Joy's screenshot if it was 32 or 64-bit
With the help of Jon Summers post, I find out that our organization's excel is 32 bit version. I guess we would probably need a 64-bit excel version, but i don't think that would be feasible in my organization. Is there maybe a workaround that makes it possbile to communicate with Excel 32 bit, while Microstation Connect is 64 bit?
Joy van Vliet said:but i don't think that would be feasible in my organization.
Why do you think that? Both 32-bit and 64-bit installers are available to those with a Microsoft 365 subscription.