We have two custom tools that read a gINT Access database and two that read home-grown Access Databases. As we looked at migrating these to ORD, we found that there is a problem accessing the Access database with a 64 bit application if the installed office products are 32 bit.
I posted a question about a gINT SDK on the gINT Forum, but if that proves to be the answer, it does not help me with the two other tools. All of these are intended to create data that none of the products deliver, or in a manner that is acceptable to the particular office the program was written for.
Mandating that our consultants use 64 bit office would probably be a stretch. Does anyone know if there is a suitable work-around?
Not exactly the same thing, but we don't seem to have an issue with ORD accessing Excel via VBA when 32-bit or 64-bit MS Office is installed on different users machines?
Regards,
Mark
OpenRoads Designer 2023 | Microstation 2023.2 | ProjectWise 2023
Can you post code snippets or screen captures of the references used to connect to Excel?
I am only an occasional VBA programmer. Our regular programmer is a consultant and I cannot task him to investigate solutions at this time, so I am doing my best to explain a problem without truly understanding the nuances of the problem.
But, I've done some digging and one of the original modules used this connection string:
g_ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0; Data Source=" & strDB
where strDB is the full path filename to the Access database.
But the Jet driver is not available in 64 bit applications, so this fails.
Without trying to rewrite code I did not author, I am looking at alternatives that still connect to a database and query the database but work in a 64 bit VBA. I realize I might be clutching at straws, but I must make the effort.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration Maryland DOT - State Highway Administration User Communities Page
Hello Chuck. I have asked our gINT developer to contact you. Expect something afternoon our time because is west coast time.
Sharing with others:
I received a reply from Bentley with a solution right after I found the same solution:
One has to "trick" Microsoft into allowing both a 32 bit and 64 bit Database Engine on a single PC. So you need to install a version that is mismatched from your version of Office. In our case, I needed to use the 2010 version of the 64 bit Access Database Engine since we are using the 32 bit version of Office 365.
Then I needed to revise my connection string from:
to
g_ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0; Data Source=" & strDB
And that was the only real change I needed to make!