In Access 2003 does anybody know how to programmatically or otherwise get rid of the nag screens for the sandboxmode, i have tried digitally signing the vba code and everything else i can think of. I'm using access developer tools to create an install package coupled with the access 2003 runtime files and i really don't want the user to have to click that they want to open the file everytime. Any input would be greatly appreciated.

Branden

Branden,

I have had the same issues this past week. M$ publishes (at http://office.microsoft.com/assistan...HA011071331033) that you can modify the macro security settings through code by using the following:

Application.AutomationSecurity = msoAutomationSecurityLow

Ok, this was the answer to my problems, but then, when I compile, it highlights msoAutomationSecurityLow and tells me that the variable is not defined. Someone else suggested I change this to Application.AutomationSecurity = 1, which I did and although the code was fine, I'm having a time of it trying to detect it on startup. I think this is something that's going to have to be done through the command line in a startup icon, but how is another story. Everything that I have found says after you change the security level, you then have to log out and back in again, so this blows what I had planned as I was going to check the level and store as a global variable on startup, change it when the app opens, then when exiting the app, set it back to the original setting. grrrrrr

The self certs sounded like a good idea, to create them when installed, but then I read that if you create queries and such on the fly that this makes the cert null and void as the code has changed. So what good is it?

At this point, unless I stumble across something else, it looks like I will need to pay approximately $325 for a Digital Cert to distribute with the app and advise the clients to list us as a trusted publisher.

If anyone else has any ideas or finds anything, please post back to the group!

Regards,

Beth M

I couldn't get that to work as well. The only solution i have found so far is to use the access runtime. The computer i tested on only had the access 2003 runtime files, no actual installation of access and it didn't pop up any of the security warnings boxes. I don't know if that is an option for you or not. If i figure anything else out, i'll post it here.

Branden

That's some good news! We deploy this as runtime but who knows how many actually take the runtime switch out when they have a full install.

Thanks for the info!

Beth M