Windows Permissions to run MS Access? (VBA References Disabled) (1 Viewer)

Stevef8

New member
Local time
Today, 11:42
Joined
Jun 22, 2022
Messages
3
Using Office 365 64-bit on Windows 10...

There's one user in our office who encounters an error when they launch a specific Access app in Access 365. The error occurs immediately upon launch, and the message is:
image002.png


Research has shown that Tools>References is completely greyed out for this user -- so the complete VBA object library is unavailable. Other users do not encounter the error, and Tools>References is enabled for them. The difference? All other users have Local Administrator permissions on their workstation; this one user does not and our IT Techs want to keep it that way.

This user can successfully run the application using an older 32-bit Access Runtime which is installed on their machine. This is considered a temporary workaround, as we'd like them to have the increased power and speed of 64-bit.

Since this seems to be a Windows Permissions issue, are there specific permissions to a Folder or other Windows resource that can be enabled for this user to allow this app to run in Access 365 without granting full Local Administrator privileges?

Cheers, Steve
 

arnelgp

..forever waiting... waiting for jellybean!
Local time
Tomorrow, 02:42
Joined
May 7, 2009
Messages
19,169
IT (domain) is controlling the permission so you need to talk to the IT to enable your app.
 

Stevef8

New member
Local time
Today, 11:42
Joined
Jun 22, 2022
Messages
3
Agreed, but while IT is willing to make changes (short of full Local Admin status), it doesn't know what specifically needs to be enabled. Got any specifics?
 

The_Doc_Man

Immoderate Moderator
Staff member
Local time
Today, 13:42
Joined
Feb 28, 2001
Messages
26,999
This user can successfully run the application using an older 32-bit Access Runtime which is installed on their machine. This is considered a temporary workaround, as we'd like them to have the increased power and speed of 64-bit.

This is a chimera. Of all the Office apps, Access is the only one that didn't change to take advantage of 64-bit addressing. Because not all of the libraries (references) migrated to x64, you actually LOSE functionality (in some cases) by upgrading from x32 to x64 for Access. Excel and Word upgraded - but Access only upgraded to support LONG LONG external addresses and a few minor things like QUAD data type for some REALLY long integers. Unless you have some very specific upgrades you needed, staying with x64 isn't the greatest choice.

The "speed and power" improvement isn't there anyway, since there is no visible difference in speed for running an x32 version on a 64-bit machine. If your unfortunate user can run the same app as other users by using Access Runtime x32 then your other users have to also be running x32 anyway. The x32 and x64 versions of an app are not cross-compatible.

As to "power" ? You won't get larger databases that way and the hardware instructions don't change their operation internally by going to x64. At most, in a VERY FEW cases, the x64 code works a little bit faster IF you are manipulating datatypes QUAD or LONG LONG, and datatypes based on DOUBLE (which IS 64-bit) were already supported in x32. CURRENCY is a typecast because it is not a native datatype in any bitness so you get nothing extra for it. That leaves me at a loss to understand "power and speed" of 64-bit unless you've been reading O365x64 advertising propaganda.
 

Users who are viewing this thread

Top Bottom