[AccessD] ADO CurrentProject.AccessConnection

[Jim Dettman]

Borge,

<< But it is failing on WIndows 11 (ARM) with Office 365 installed.>>

  What version of Access are you working with; 32 or 64 bit?

<< On Windows 11 ARM in Access VBA the default reference is set to the same
C:\Program Files\Common Files\System\ado\msado15.dll>>

 This would imply that you are working with 64 bit.

I would try this first:

1. Uncheck the ADO reference.
2. Close the DB and Access.
3. Open Access and the DB with the shift key held down.
4. Check any reference in the list besides ADO.
5. Close the DB and Access once again.
6. Open Access and the DB with the shift key held down.
7. Un-check the reference you just checked (will be last in the list).
8.  Now scroll down and find the correct ADO reference and check it.
9.  Do a compile.   Make sure it's error free.
10 Close the DB and Access.
11. Re-open and test.

Steps 1-7 forces a refresh of the refences in VBA and will clean-up any
hidden problems.

If the above fails, then you have some kind of problem with the Access
install.

Next stop would be to use regsrv32 and un-register and re-register the DLL.
Note that there are two versions of regsrv32, Windows\System32  is for 64
bit, and Windows\sysWOW64 for 32 bit.

Failing that, and un-install/re-install of office.

HTH,
Jim.

-----Original Message-----
From: AccessD On Behalf Of Borge Hansen
Sent: Tuesday, September 10, 2024 1:08 AM
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: [AccessD] ADO CurrentProject.AccessConnection

Hi all,
On my Windows 11 (ARM) system I have Office365 installed on my laptop as a
VM (using Parallels on a M1 Apple Macbook).

As part of setting up an ADO recordset on a local table in the frontend I
am using the
CurrentProject.AccessConnection as the connection string.

This is working forever - currently on Windows10 with Access 365 64bit on a
lastest terminal  WIndows Server with Access 2016 32 bit.
But it is failing on WIndows 11 (ARM) with Office 365 installed.

Using an empty Access .accesdb file with the only other reference than the
default ones being
Microsoft ActiveX Data Objects 6.1 Library

I can successfully in VBA run in the immediate window
?CurrentProject.AccessConnection
And I get similar to this response:
Provider=Microsoft.Access.OLEDB.10.0;Persist Security Info=False;Mode=Share
Deny Read|Share Deny Write;Data
Source=C:\Users\Borge\Documents\bshADO_TEST.accdb;User ID=Admin;Data
Provider=Microsoft.ACE.OLEDB.12.0

On the latest Windows Server the reference to
Microsoft ActiveX Data Objects 6.1 Library
is held in C:\Program Files (x86)\Common Files\System\ado\msado15.dll

Similar on Windows 10 64 bit with Office365 64 bit, where the reference
location defaults to:
C:\Program Files\Common Files\System\ado\msado15.dll

On Windows 11 ARM in Access VBA the default reference is set to the same
C:\Program Files\Common Files\System\ado\msado15.dll

But I always get the run time error 429:
"ActiveX component can't create object"

On Windows 11 (ARM) there is also this folder with a msado15.dll version
C:\Program Files (arm)\Common Files\System\ado\msado15.dll
plus quite a number of other folder locations with a msado15.dll file

However
- I can't in Access VBA browse and point the
Microsoft ActiveX Data Objects 6.1 Library
to that folder and file.
- I cannot move the (arm) version of the msado15.dll file to the default
folder reference for
Microsoft ActiveX Data Objects 6.1 Library in Access VBA

I have reached a dead end!

Can anyone help spread some light on this - provide a solution?

Shane?

Thanks,
/borge
-- 
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com