A potential security concern has been identified (1 Viewer)

[JohnPapa]

My software user A13 Runtime and the pcs have Office 19 (32-bit) installed.

On submitting an update (new .mde), I got the message above which I was able to get rid off in the past. The BE is accessible through a mapped drive (V) on a local server.

I changed the following Registry setting on one of the pcs

[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Access\Security\Trusted Locations\Location(20)]

"Path"="V:\"

No luck.

I will try to reinstall the software with the Runtime again.

Any ideas?

On my laptop it works fine. It used to work fine on the specific PCs.

 

[Cronk]

Try using the URL in the backend table linking

\\servername\folder\folder\BEfilename.accdb

 

[Pat Hartman]

Microsoft has added new rules in Windows regarding VBA and some of your PCs may have the new rules being implemented and some don't. I don't know if anyone has yet made a sticky, but hopefully one of the experts will so we can link to it to offer work arounds.

 

[JohnPapa]

Try using the URL in the backend table linking

\\servername\folder\folder\BEfilename.accdb

The path that the files link to are defined by the mapped drive

 

[JohnPapa]

I reinstalled the runtime and the software. No luck.

Any help would be appreciated.

 

[Eugene-LS]

I changed the following Registry setting on one of the pcs

[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Access\Security\Trusted Locations\Location(20)]

"Path"="V:\"

No luck.

You should change number to MSO installed in string:
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Access\ ...

For MSO 2016 and above like this:
... Office\16.0\Access ...

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Access\Security\Trusted Locations\Location0]
"Path"="D:\\My MSO Projects\\"
"AllowSubfolders"=dword:00000001

In your case (MSA 2013 Runtime):

[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Access\Security\Trusted Locations\Location20]
"Path"="V:\\"
"AllowSubfolders"=dword:00000001
"Description"=""

 

[JohnPapa]

I believe I did what you mention above.

Please see attachment.

 

[Eugene-LS]

Please see attachment.

Check out please: is folder setted right way

 

[JohnPapa]

Check out please: is folder setted right way

I checked what you mention and I even created a new folder V:\aaa\ just in case it did not like writing to the top directory.

It gives me the message about 20 times and there are many more tables in the BE.

Also, once I click on the message 20 times or so, it works fine.

 

[Minty]

This is a guess, as I can't test it very easily, but as @Cronk suggested I don't think a drive path that isn't a UNC path will work.
It's something to do with the drive not always being available, whereas a UNC path should be.

 

[isladogs]

In post #1, you showed ... Location(20). It should be ...Location20
Remove the ( ) brackets

 

[JohnPapa]

I had not used the brackets in the actual registry entry.

I also tried other numbers like Location222.

Same problem.

 

[JohnPapa]

Would a security certificate help in any way?

 

[isladogs]

No, it wouldn't.
I think the problem is an incorrect entry for AllowSubFolders.
The Type should be REG_DWORD not REG_SZ and the value data = 1 as shown below.

 

[JohnPapa]

Thanks for pointing it out. I changed to the following which still does not work. For Path I tried V:\ and V:\\

For a Local Path, it works. C:\VisualDentist\

 

[isladogs]

Several points:
1. AllowNetworkLocations to be trusted (or not) is a global setting and should be in the root folder ONLY

I normally leave this setting unticked

2. The folder should be V:\ not V:\\

3. If still a problem, try resaving the file as an ACCDE.
I do sometimes get security messages for MDE files downloaded from the web even when in a trusted location ...but never for ACCDEs.
Mind you the rules are about to change again ....

 

[JohnPapa]

After many hours of frustration, it is now fine. Many thanks IslaDogs.

Is there some place to note that this solved the problem?

 

[isladogs]

Hooray.
For the benefit of others, please confirm what the fix was
Yes - there is a setting to mark your thread as solved but my brain has gone blank as to where it is.
Hopefully someone else will step in

 

[The_Doc_Man]

Depends on how it was initially posted. Can't solve a non-question.

HOWEVER, scroll to the first post of the thread and see if the "solved" button appears just above that post in a short set of menu-bar tools. If so, you can click it.

 

[KitaYama]

Above the page