Solved Security Risk Microsoft has blocked.....

[vanzie]

Hi everyone.

To avoid duplicate thread, please direct similar solved post.

I am running Windows 11 on a administered network. The front end and back end file is on th same share drive but back end is password protected and since many users are utilizing the FE, the BE is linked through network path and not assigned network drive letter.

Some computers allows the databse to run, but some don't, like my laptop. When I open the FE, the Security Risk banner pops up stating Microsoft has blocked macros from running because the source of the file is untrusted.

I have lowered the internet settings to allow the source as trusted...does not work. I have set every folder on the share drive as trusted via Trust Center....does not work. Is there any other possible way to bypass or accept the database file as trusted?

 

[arnelgp]

right click on the db and on it's property, Unblock it.
internet setting has nothing to do with this.

 

[vanzie]

right click on the db and on it's property, Unblock it.

There is no such option. I've just set up the share drive on another employee's PC and started the database. It gave me the same error but showed me the message bar to Enable Content and added to file as Trusted. No problem whatsoever.

I've relinked all tables to the back end file and removed all Macros and replaced them with VBA. Still the same issue

 

[KitaYama]

In some cases Microsoft doesn't allow a network path to be added to trusted location. I don't know why and when, but I've seen it several times.
Some of my PCs can set a network path to trusted locations, some can not.
You have to save the FE in a local path in your PC and add the folder to trusted location. You will never see that message.
But
If the FE is in a local path and the folder is not set as trusted location, the button @arnelgp explained will be shown

 

[arnelgp]

There is no such option. I've just set up the share drive on another employee's PC and started the database.

did you Split your db. If you are using "share" backend, surely you must split it and all users has their own FE.

 

[vanzie]

In some cases Microsoft doesn't allow a network path to be added to trusted location. I don't know why and when, but I've seen it several times.
Some of my PCs can set a network path to trusted locations, some can not.
You have to save the FE in a local path in your PC and add the folder to trusted location. You will never see that message.
But
If the FE is in a local path and the folder is not set as trusted location, the button @arnelgp explained will be shown

The local path seems to work on my PC. The reason why I don't want to distribute the FE locally is because they always tend to forget or they intend to mess things up and on a daily basis help to recover their files.

But if it has to be done, it has to be done. So far had no problems using one FE on the network drive.

Thanks for the assistance.

 

[AHeyne]

Some of my PCs can set a network path to trusted locations, some can not.

Maybe it depends on the specified type of network of your NIC (public, private, domain)?

 

[moke123]

I think KitaYama is referring to this

 

[AHeyne]

Yes, but maybe this first option is disabled on some of his PCs because of the network settings.
Maybe there is a rule to not allow this on public networks.
It's just an idea.

 

[moke123]

But if it has to be done, it has to be done. So far had no problems using one FE on the network drive.

recipe for disaster, as is using wifi on laptop.

 

[KitaYama]

Maybe it depends on the specified type of network of your NIC (public, private, domain)?

It's a the network on the same domain. All PCs are clients of a windows domain. All on windows 10. All the same version Microsoft 356.

 

[KitaYama]

I think KitaYama is referring to this

View attachment 113497

I've already tried that. Even selecting that, browsing to a network path, and selecting a folder, Access warns me that the folder can not be trusted.
I had a thread on this somewhere and it never solved.
If you google it, you'll see a lot of those who have faced the same error.

 

[AHeyne]

It's a the network on the same domain. All PCs are clients of a windows domain. All on windows 10. All the same version Microsoft 356.

Should be I would say. I've seen misconfiguration in Windows caused by whatsoever, where the domain status of the network was gone.

 

[KitaYama]

Should be I would say. I've seen misconfiguration in Windows caused by whatsoever, where the domain status of the network was gone.

As I said I really don't know what's happening behind the curtain. Maybe you are correct. But even you are guessing:
"Maybe it depends on...."

Microsoft doesn't say anything about this and if you google it you'll see how many people are facing this problem.
one is here:

Redirecting

 

[AHeyne]

Of course, this is just a guess. But I've learned to think a little more broadly when troubleshooting when you're stuck. ;-)

 

[moke123]

Did you remove the mark of the web, if there is one?

 

[KitaYama]

Did you remove the mark of the web, if there is one?

May I ask whom you're asking? Me or the OP?

 

[The_Doc_Man]

Just for reference purposes, "Mark of the web"...

Is there a way round the - "Mark of the Web"

I understand that Microsoft will be blocking VBA soon, in all files from the web. - Re "Mark of the Web." I was wondering if there was a way round the the Microsoft induced problem for downloaded MS Access databases containing VBA. I thought, how would Windows know if an MS Access dB contained...

www.access-programmers.co.uk

 

[DickyP]

The reason why I don't want to distribute the FE locally is because they always tend to forget or they intend to mess things up and on a daily basis help to recover their files.

I don't follow the logic of this this reasoning! 1) what do they forget? 2), how is messing up a local FE a bigger problem than messing up a network one which affects all users? 3) Lastly if people intend to mess things up this is a disciplinary matter.

I suspect, however, that this paragraph just needs rephrasing or explaining better.

 

[Pat Hartman]

The reason why I don't want to distribute the FE locally is because they always tend to forget or they intend to mess things up and on a daily basis help to recover their files.

We do this by using one of two methods.
1. a database that downloads the FE and runs it
2. a batch file that downloads the FE and runs it

You place the FE in a master folder on the server. You create a shortcut that runs the batch file or that opens the distribution database. There are several variations of the distribution database posted here. Someone can give you a link if you can't find one. I use the batch file method since it is very simple. 4 lines of code.

create the local directory
delete an existing copy of the local FE
copy the FE from the server to the local drive
Open the FE

Missing from the batch file method is version checking. I include that in the main application using two tables a Server table and a Local table. If the versions don't match, the FE won't open. This is safer than having the distribution database do the version checking because it works if the user finds a random version of the FE and just opens it.