Link to home
Create AccountLog in
Avatar of LJG
LJG

asked on

Trust Center Access 2010

Am I missing something - Trust Center?  Access 2010

It would appear to me that if someone installs my application on their computer, they load the app, they answer "Enable Content" in the security warning.

From that moment on - they will not get the security warning when they open the App.

If the above is true - What if I update the app.  Today I have version 1 of MyApp.accdb and tomorrow i have version 2 of MyApp.accdb.

I know I can set the trusted location, buy a certificate, but if the above is true, it gives me another options.

Thanks in advance for your help.
LJG
ASKER CERTIFIED SOLUTION
Avatar of Dale Fye
Dale Fye
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
You will also want to set Macro (in)Security to LOW.

"I know I can set the trusted location"
You *need* to do this :-)

mx
You don't need to set macro security to LOW if you put the application in a trusted location.  That is the whole point of a trusted location.

At least that is true for 2007, my 2010 version is on my home laptop, and am not able to check that at the moment.
Joe,

My bad.  As the Fonz would say, you are cccccccorrect.
Was the Fonz the first to say that ?

You would THINK - you would not need LOW if you have TL, but in reality, that's doesn't play out. So, I modified my TL Reg script to include setting the Reg value also. We have a lot of peeps being upgraded to Win 7, so they need to run my script. Everyone had previous run it on their WinXP / O2010 systems.

mx
Joe,

Actually, as I recall, the Fonz used to stumble over the word "wrong".  So rather than admit that I was "wrong", I will concede that you were "correct".

Have a nice Memorial Day, remember our fallen.

Dale
"remember our fallen."
Don't get me started!
Avatar of LJG
LJG

ASKER

Showing my ignorance -  What appears to be a fact to me - if you could tell me where I am wrong.

On my laptop / Win 7 Prof / Access 2010

1) The only "Trusted Location" is C:\Program Files (x86)\Microsoft Office\......
2) I've copied a test app (just front end no back end) to C:\Test\MyApp.accdb
3) I open the app in Access 2010 and it asks me "Enable Content"
4) After I click "Enable Content" button the first time I can close Access / Close Windows 7 / Turn off the machine, etc. and it never asks any questions again.  It just loads and all the code works.


Settings --> File / Options / Trust Center / Trust Center Settings / Macro Settings is set to
Disable All Macros with Notification

With the above discussion - I obviously am not understanding something.

Thanks for all the help.
I'll have to wait until I can get home and test it on my Win 7 Pro / Access 2010 laptop.  Out of interest, are you using the 32 or 64 bit version of Access?
Avatar of LJG

ASKER

I'm using 32 bit version.
thanks
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of LJG

ASKER

DatabaseMX
Appreciate the feedback - but I'm looking at understanding the security info for my customers.

So I understand how you are solving the problem for My computer, but am I wrong on the below?

    1) If I have a customer in a department of a big corporation that is using a program I built
    2) If the IT department is nervous about making a number of "Trusted Locations"
    3) If I can convince them to set Macro Security to -->Disable All Macros with Notification

If the above is true it would appear to me - the user would click "Enable Content" button the first time and everything works for the rest of the applications life?

Basic Question - am I wrong on the above?
"button the first time and everything works for the rest of the applications life?"
Well, I'm not sure. I have a Database Loader that copies Front End Masters to a local workstation. So, it's like getting a new db each time. Without the Low setting, they get that message each time ... which related to:

If the above is true - What if I update the app.  Today I have version 1 of MyApp.accdb and tomorrow i have version 2 of MyApp.accdb.

If you deploy a new physical version, they will get the message again. Trusted Locations is a separate issue. Without a TL, then you can only run the 'sandbox' functions as far as I can tell, so - that is completely useless.  Essentially, mosit all important built in functions and the code that uses them will not run.

mx
Avatar of LJG

ASKER

Again - I Appreciate the feedback - and if everyone just disagrees with me, I'm willing to split the points  between DatabaseMX and fyedP and be on my way.  But if what I am saying is true - It's on OPTION for people who write Access databases imho.

I am saying the following works even when you update the program - with my experimentation.
    1) No  "Trusted Location" in the folder the application sits
    2) IT department sets Macro Security to -->Disable All Macros with Notification

    3)  Install the program - Day 1 - User clicks --> "Enable Content"
         Everything (code / macros / etc.) works for the rest of the applications life.
         a) Day 2 Everything works - No need to "Enable Content"
         b) Day 30 - big update - new objects in the database / database bigger in size  - No need to "Enable Content"
         c) For the applications life - including update (file name has to stay the same) - No need to "Enable Content"

If anyone disagrees - if you could tell me
         1)  You have tried the above and get different results
         2)  The above works but it's not a good option - and explain why you think so.

Thanks for any help.
LJG
") IT department sets Macro Security to -->Disable All Macros with Notification"

Well, are you sure it's the IT Dept doing this?  That is the default setting out of the box.

In your 1,2,3 above --- I think yes ... you will not get the Enable content msg.

As I have found, there seems to be a lot of confusion regarding Trusted Locations and Macro Security ... as is  some inconsistencies ...

mx