dBase issue with Office 365 64bit

[juneau730]

Morning all,

I have a pretty robust and complex Access dBase used for auditing a lot of user data, that was build on Office 32bit. Recently some users have upgraded to Office 365 64bit and the dBase isn't working properly anymore.
One issue, that I was able to fix was the Declaration in the various scripts. Added PtrSafe after the word Declare and that issue went away.

Now, we are getting an error pertaining to the ADODB.Connection. We are getting "ADODB.Connection: Provider cannot be found. It may not be properly installed. "

Many of the scripts have the following code in it, all of which work for the 32bit Office, and this is the line(s) in the code the error message are pointing too.

Sub CreateDBConnection(strTargetData)
    'connect to database
    Set objConn = CreateObject("ADODB.Connection")
    objConn.open "PROVIDER=Microsoft.ACE.OLEDB.16.0;DATA SOURCE=" & strTargetData
End Sub

The only thing I can think of is that the OLEDB version is incorrect for Office 365 64bit, but, the office Version is 2402 Build 16.0.17328.20670, so I don't know for sure.

Any help would be great.

 

[juneau730]

Good day all,

Much of the research I have done, indicates that the OLEDB for Office 365 64bit should be set at OLEDB.12. I've tried that and it didn't resolve the issue.
The scripts are pulling the data from the source, creating the appropriate spreadsheets, formatted correctly, but not importing them into the dBase, due to the ADODB Connection error.

I'm at a loss now and could truly use some help with this,

 

[welshgasman]

Does this help?
I think you are going to have to use compiler directives to state which driver to use?
Same as you woulf for any APIs?

Download Microsoft OLE DB Driver for SQL Server - OLE DB Driver for SQL Server

Download the Microsoft OLE DB Driver for SQL Server to develop native Windows applications that connect to SQL Server and Azure SQL Database.

learn.microsoft.com

 

[juneau730]

Does this help?
I think you are going to have to use compiler directives to state which driver to use?
Same as you woulf for any APIs?

Download Microsoft OLE DB Driver for SQL Server - OLE DB Driver for SQL Server

Download the Microsoft OLE DB Driver for SQL Server to develop native Windows applications that connect to SQL Server and Azure SQL Database.

learn.microsoft.com

Good morning,
Thanks for the information. After looking at it yesterday and comparing setting on both systems running both 32bit and the 64bit version of office, neither have that installed. The dBase isn't talking to a SQL server, it's locally installed and run (on local PC).
Though I may be incorrect in thinking this, but since it's not installed on any system, and those running 32bit Office all work (100s of them) this may not be the cause of the different routines creating a connection to the dBase and importing the data.

 

[juneau730]

I should also say that the system in question for have both OLEDB "drivers" installed.