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: 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
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.
Barry Lothian said:Why do you think that?
Perhaps it's the position of IT rather than an individual.
64-bit versions of Office (or any other VBA implementation) lose access to UI widgets that are familiar in 32-bit VBA. For example, the ListView is a popular and versatile add-on (OCX) that displays multi-columns text and icons. The VBA built-in ListBox is pedestrian by comparison. Microsoft have declined to make 64-bit versions of that OCX, and several others, including the Common Dialogs.
Barry Lothian said:Both 32-bit and 64-bit installers are available
Yes, but you can't install both on the same computer. Microsoft mandates that you choose either 32-bit or 64-bit Office — it's exclusive-or.
It's like what you said, it's unfortunate not in my position to request for a 64-bit version, but more of the higher ups and IT (since the organization is quite big). I didn't know though about the 64-bit version losing UI widgets. That's good to know. Is there maybe a workaround that I can use a csv file instead of an excel and circumvent this problem? In excel there are 4 columns and each column consist of different information which form the ouptput of the four dropdown list in the form. I still need this functionality of having four dropdown lists, but I am not sure whether this might be achieved with a csv file.
Joy van Vliet said:I am not sure whether this might be achieved with a csv file
CSV is dumb data — it doesn't do anything. However, it's a neutral format and doesn't care whether VBA is 32-bit or 64-bit. It should be straightforward to write a CSV file from Excel and read it into MicroStation using VBA.
Joy van Vliet said:but I am not sure whether this might be achieved with a csv file
Before you even consider that, lets go back to your original post for a moment; your screenshot shows code relating to a Database. Have you tried making a connection to that same database from Excel instead?
You've also not given any details on what the macro does i.e. what information from MicroStation are you working with and what does your macro do with it?