Trusted with Distributed project?

[Kirsten]

I have an Access app that I want to distribute to some user. What can I do so that they don't run into Not a Trusted Site error?

[mshmyob]

Create a text file with the .REG extension and put this in it and it will eliminate the Trusted Location on your computer.

Run this file on any computer you want to install the runtime on.

This will eliminate needing a trusted directory and will remove the message from Runtime.

Is this what you want?


Code: ( text )
REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\A ccess\Security]
"VBAWarnings"=dword:00000001


cheers,

I have an Access app that I want to distribute to some user. What can I do so that they don't run into Not a Trusted Site error?

[missinglinq]

Changing the system settings of other users machines is highly frowned on, and changing the registry is never something to be done lightly! Changing it on clients machines sounds like a recipe for disaster to me. The Trusted Location is there for a reason, and probably should be left in place for others apps that may come along. I'd simply notify the customers that the app needs to be declared as Trusted, with the directions for doing this if need be.

Linq ;0)>

[mshmyob]

I agree, the problem with the Access 2007 runtime is that even if you set the trusted directory and everything correctly it still always pops up when starting an app.

After a lot of research this was the only way I found to disable that message.

cheers,

Changing the system settings of other users machines is highly frowned on, and changing the registry is never something to be done lightly! Changing it on clients machines sounds like a recipe for disaster to me. The Trusted Location is there for a reason, and probably should be left in place for others apps that may come along. I'd simply notify the customers that the app needs to be declared as Trusted, with the directions for doing this if need be.

Linq ;0)>

[missinglinq]

I knew there was something else I meant to say. Unless I missed something, nothing in the OP's post mentioned Access Runtime, did it?

BTW, is the problem you mentioned still there with the just released SP1 for the runtime version?

Linq ;0)>

[mshmyob]

After I responded to you I was wondering the same thing (if they fixed the problem with Runtime SP1). I haven't had a chance to test it yet.

I will say that it is the most annoying thing and clients hate that message popping up with runtime. Typical MS, you follow everything to the 'T' and it still doesn't work. I'm not complaining though since the runtime is free and I really do like the new Access (in particular the custom ribbons - they really give the app a nice look and feel).

I know the OP didn't mention Runtime but it appeared to me that they knew about setting the trusted locations in the main Access and since that works I assumed runtime.

Also if it isn't runtime they will let me know (lol).

cheers,

I knew there was something else I meant to say. Unless I missed something, nothing in the OP's post mentioned Access Runtime, did it?

BTW, is the problem you mentioned still there with the just released SP1 for the runtime version?

Linq ;0)>

[Kirsten]

Runtime.
If I didn't mention it in the text I was certainly thinking it. So thanks for reading my mind (usually in a font too small to be noticed).

[mshmyob]

Woohoo... Mark 1 for me...

cheers,

Runtime.
If I didn't mention it in the text I was certainly thinking it. So thanks for reading my mind (usually in a font too small to be noticed).