Error when opening a program inAccess in win 8.1

I have used a DB program in in Access 2010 and win7 for years with no problem.
Since I switched to win 8.1 I get an error message upon opening. If I click on OK 3 times it runs fine, but I would like to eliminate the hassle of extra keystrokes.
The program has a file extension of FileName.Mde
I have enclose a screen shot of the error. I sure would appreciate any heplp or ideas.
Floyd

 

Hey floyd...

It's just a perception of mine, but it seems to me that as MS programs get older (such as the Office versions), MS tends to burden them down with silly security "features". It really makes me a little bit angry I have to say, but I wonder if this is the issue you are facing. Given that Office 2010 is not specifically written for Windows 8 or 8.1, etc., I think it's possible that either a security patch for Office 2010 or a Win 8 security patch is the source of these messages. Maybe it's just plain built into W8...not sure.

I have seen MS' phony brand of after the fact security creep into Office 2007. I download a "security" patch and all of the sudden features are unusable, and I have to track down the setting, etc.

This in mind, I'm not sure if your issue is Windows or Access related. I suspect Access, however. Here is a link that might be of some help:

http://stackoverflow.com/questions/...warning-at-the-startup-of-a-ms-access-project

You may be able to find more at Google search [security warning office access 2010]

 

I'm wondering if turning off UAC would solve the issue (BTW, I don't know how to in 8.1). The screen I saw indicates it's a Windows 8.1 message.

 

I don't have access 2010, but I do have access 2013. You need to open access by itself, then click on File, options, then Trust Center, Click Trust Center Settings, Trusted Locations, then add the path to the database in question.

I've also had to enable macros under Macro Settings (If you use macros). I know this is a big security risk, but sometimes you have to open doors.

Close, then try to open your access database.

At work, we had to go through many hoops to upgrade from 2003 to 2007 and then 2010. I look (not) forward to when we upgrade to 2013 when we go with O365 next year.

 

Thanks all. Problem solved.
I appreciate everyone's effort.:wave
Floyd