Always get Security Warning even though no macros

[G6ET]

First post. I always get the "Certain content has been disabled message" when opening database files in Access 2007. This occurs even when the mdb or accdb file is completely empty. No tables, no queries, no macros. I know I can change my trusted locations etc but I would like to know what the "Certain content" is that causes this. Same thing happens in Excel. Why is it so?

 

[ajetrumpet]

google this. this happens by default. and millions have already asked the question, so you're not alone: http://www.accessforums.net/security/security-warning-content-disabled-how-get-round-3182.html

http://www.accessforums.net/security/security-warning-content-disabled-how-get-round-3182.html

 

[G6ET]

Thanks for the response. Found those links in my own google searches before posting. Everything I've found relates to database files that actually have macros etc. Makes complete sense to have to change trust centre settings etc if the file has some sort of content... but even a empty file??

 

[SOS]

If you open a database, even an empty one, you cannot do certain macro actions unless you have activated code and macros or set the database location as a trusted location. So this content has been disabled. It is the fact that certain portions of the database designer (as well as the database) has been disabled due to this.

 

[G6ET]

OK, I guess that makes some sense. It's an annoyance rather than a problem for me, but I now see the logic. Thanks for your help. Gold star to you!

 

[SOS]

OK, I guess that makes some sense. It's an annoyance rather than a problem for me, but I now see the logic. Thanks for your help. Gold star to you!

The annoyance is easy to overcome. Just move the database to a trusted location and if you don't have one set, set it and then it won't give you that message again.

 

[G6ET]

The annoyance is easy to overcome. Just move the database to a trusted location and if you don't have one set, set it and then it won't give you that message again.

Yeah, have that covered - just couldn't figure out what was causing offence, but your explanation clears that up. Just a bit painful when you send stuff to people and have to explain to them how to change their settings