Call Access 2003 database runtime without security warnings

[Hypermommy]

Hi y'all,

Not sure if I'm in the right place so maybe a mod will move me if I'm wrong. I've got this program I'm working on in VisStudio2008. Basically, it accepts a password and executes an Access 2003 database using the Access 2003 runtime. I've got the thing looking up a password and all is good, but there's one problem.... those annoying Access 2003 and higher warnings about unsafe macros. Does anyone know a way to make sure those don't show up when the program starts?

My client has a database that someone else wrote for her. She's not at a point where she could have it rewritten (believe me, I've tried to talk her into that). So I have to stay in Access but it's not very professional to have those warnings come up. Any way around them?

Thanks!

[.paul.]

that sounds like a VBA question

[gep13]

Hey,

Not sure if this a VBA question, but rather a project that attempts to automate Access.

Hypermommy, can you provide more information about what exactly you are creating?

I think I am right in saying that the pop up's that you see are based on the setting in Access itself, in the same way as you get marco security errors when you open Excel. You should be able to edit the security permissions so that they don't pop up.

Gary

[Hypermommy]

Be happy to provide more info. Not exactly sure what'll be useful so let me try to provide as much as possible (and please forgive if it's too much). Basically, my code authorizes the user. Once the user's authorized it uses this snipped to open the Access database.

Dim oProcInfo As New ProcessStartInfo
oProcInfo.WindowStyle = ProcessWindowStyle.Maximized
oProcInfo.FileName = "D:\Program Files\Microsoft Office\Office11\MSACCESS.EXE"
oProcInfo.Arguments = " /runtime """ & sPath & "\patientpractitioners.mdb"""
oProcInfo.WorkingDirectory = "D:\Program Files\Microsoft Office\Office11"
Dim myProcess As New Process
myProcess.StartInfo = oProcInfo
myProcess.Start()

But when I open Access I get the security warnings in Access. Yes, you're right that they're the warnings in Access, same as you'd get in Excel. If this database were just going to be run on my machine or my client's machine I could set the security settings to low and wouldn't have this problem. But my client is going to be selling this application to other folks and I don't believe putting security settings to low is something they're going to be able to tell their customers to do (I know how I'd feel if I bought something and that was part of the deal... it'd make me wonder).

Ideally, I'd like to find something that I can do in my VB.NET program that would temporarily set the security settings to low and then return them to whatever the user had when my program exits.

[gep13]

Hey,

So, it's definitely not a VBA issue you are having then.

As for how to go about fixing it though, I am really not sure. There may be some settings that you can put on the MDB file, or some parameters you can pass through to the Process.Start method that will by pass the security checks, but really not sure.

Hopefully someone will come along with an answer for you though.

Gary

[gep13]

Hey,

I have just done a quick google, because I was curious, and I found the following website:

http://www.accessmvp.com/JConrad/acc...osecurity.html

Point number 9 seems to have a way to get round this from a VBScript side of things, so you may be able to do something similar.

Gary