Access Runtime for Microsoft 365 (1 Viewer)

KACJR

Registered User.
Local time
Today, 17:42
Joined
Jul 26, 2012
Messages
117
Greetings, my friends...

Most staff at our remote sites have Microsoft 365 Business Basic licenses (because they're free for non-profits). As you know, this means that users have access to the web-based Office apps only. We updated our Access Runtime 2016 to Access Runtime for Microsoft365 in order for our Access apps to run in those environments. We were able to successfully test the apps using Runtime on a test PC configured as one of our residences.

We deployed the new Runtime to one of our remote users. Back when we were running Access 2016, we'd get a warning about macros being dangerous but we could just allow it and then Enable Content. Not so with the new Runtime. When we attempted to launch one of the apps, we received an error indicating that Microsoft blocked the app because it uses macros (which I think also applies for apps that use VBA). However, there was only a cancel button, not the OK button that would allow you to override the block. Instead, Microsoft directs me to open a desktop app and go to the Trust Center. But since these locations do not have desktop apps, there's no Trust Center to go to.

Why Microsoft did this, I have no clue. What Access app doesn't have either macros or VBA code?

Has anyone encountered this and found a way to get beyond it?
 
I merge a reg file named TrustLoc16.reg that adds the location of my FE to the trusted location list for office365 and runtime2016.

Code:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Access\Security\Trusted Locations\Location0]
"Path"="C:\\PathToYourFE\\"
"AllowSubfolders"=dword:00000001
"Description"=""
"Date"="3/24/16 3:34 PM"

With the file on the users computer, right click on it and select merge.

1772212297209.png
 
I merge a reg file named TrustLoc16.reg that adds the location of my FE to the trusted location list for office365 and runtime2016.

Code:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Access\Security\Trusted Locations\Location0]
"Path"="C:\\PathToYourFE\\"
"AllowSubfolders"=dword:00000001
"Description"=""
"Date"="3/24/16 3:34 PM"

With the file on the users computer, right click on it and select merge.

View attachment 123347
What is the Date value?
 
It's dangerous to try to run Access databases from OneDrive, or any other similar location such as DropDox. Others have written extensively of the reasons for this warning, so I won't repeat it again. I urge you to search out guidance on avoiding OneDrive with Access databases. One good starting point might be here. It links to other reliable sources. Read them all to get the full picture.


In short, you are flirting with disaster by allowing OneDrive usage with your Access database application.
 
It's dangerous to try to run Access databases from OneDrive, or any other similar location such as DropDox. Others have written extensively of the reasons for this warning, so I won't repeat it again. I urge you to search out guidance on avoiding OneDrive with Access databases. One good starting point might be here. It links to other reliable sources. Read them all to get the full picture.


In short, you are flirting with disaster by allowing OneDrive usage with your Access database application.
So I should put the FE in a non-QneDrive folder and put a shortcut on the Desktop.
 
So I should put the FE in a non-QneDrive folder and put a shortcut on the Desktop.
In most scenarios, I believe the preferred location is a folder on the computer used by the user. A copy of the FE should be copied to those folders for each individual user.
 
I would not put a FE on OneDrive, because it will be trying to sink every change while you are working with it.

In most scenarios, I believe the preferred location is a folder on the computer used by the user. A copy of the FE should be copied to those folders for each individual user.

For testing purposes, I created C:\AccessDatabases, copied the front-ends to this folder. Unblocked the FEs, then made shortcuts of all of the FEs to my Desktop. One thing I noticed immediately is the FEs are launching quicker and processing quicker.
 
I setup a folder on the C: drive for all Access FE files. That folder is added to Trusted Locations. Really no different from how most software is installed.
 
From a very strict reading of how OneDrive works, a front-end CAN reside on a OneDrive folder. HOWEVER, that file CANNOT be shared among multiple users. It must be a private and separate copy for each user AND you can NEVER use FE-resident tables as a way to optimize lookups. Other issues might also crop up related to code in the FE adjusting its own the settings (i.e. the FE changing itself), which IS theoretically possible for a .ACCDB file but not at all recommended.

The SAFER and FAR more reliable method is to have private copies of the FE on each user's workstation. You COULD have a copy of the FE on a OneDrive that everyone could copy to their local machine. But actual file sharing on a OneDrive file is a forlorn hope at best and a train wreck at worst.
 

Users who are viewing this thread

Back
Top Bottom