Warnings problem

[mafhobb]

Hello.

I have just finished my second 2010 database and I have distributed it among the users. This is a split database with and encrypted be and an accbe front end.

The be is on a company network drive while the fe is on each user's computer. I have a custom login form and the warnings are set to false on frmlogin formload.

Me and a few other users do not have this problem, but others, with computers seemingly setup the same as mine run into an error message at startup "A potential security concern has been identified" and it lists the location of the fe. If the user clicks on Open, he can actually open the database although he gets a yellow bar at the top saying that "This database has been opened as Read-Only".

Both the fe and be paths and its subfolders have been added to the trust security center. Activex warnings and Macro settings have been changed to "allow or enable". The message bar has been set to "Never show information about blocked content", and the "allow documents on a network to be trusted is checked." Several of the affected computers have been set to the exact same settings, but the warnings keep shown up.

I am out of ideas. Why is this message showing up and how can I remove it from everyone's computers? Why is it not showing up in mine but it shows up in other computers with the same trust center setting?

Help, please

mafhobb

 

[NeutronFlux]

I'm guessing the warning you turned off is probably for the warning messages that pop up when you're about to delete records and stuff (DoCmd.SetWarnings False). There's no VBA or Macros to automatically turn off the trust warnings on startup as no VBA or Macros are run while the application is untrusted. At best, you can turn it off AFTER you've trusted it once.

Are you using UNC paths? If not, try switching either everything to it or everything away from it and make sure the shortcuts or whatever shows up in the address bar of explorer are the same.

Also, trust settings are saved in the computer's registry entries. I can't remember what the entries are off the top of my head, but you should be able to find them if you search around. I think the Access Deployment package can set it automatically (is it out yet for 2010?). If all else fails, and you know how to use registry editor, you can try to check the registry entries directly.