![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, We have a client complaining that every time they start up their MDE, they are getting the "Unsafe Expressions" security warnings. And one of them says that to block unsafe expressions, Jet 4.0 SP8 or later must be installed. He said he has run Windows Update and that their are no more updates. Is it possible to suppress these messages? Thanks, -paulw |
#3
| |||
| |||
|
|
Nevermind. The guy had me confused. I "made" him click YES to block unsafe expressions and the messages went away. |
#4
| |||
| |||
|
|
PW wrote: Nevermind. The guy had me confused. I "made" him click YES to block unsafe expressions and the messages went away. And that might very well make his apps not function. I just tell users to change the macros - security setting to "low". No more prompts and perfectly safe as long as they don't go around downloading unknown Access files from the web and running them. |
#5
| |||
| |||
|
|
Rick, How would I do that when creating the MDE? Is it possible I could do it on my end and ship our application with macro security set to low? Some of our users do not have Access installed and I certainly don't think they could handle opening up Access and setting the macro security even if they did. I also found code on the Internet that can be run to edit their registries but I don't want to go there! |
#6
| |||
| |||
|
|
PW wrote: Rick, How would I do that when creating the MDE? Is it possible I could do it on my end and ship our application with macro security set to low? Some of our users do not have Access installed and I certainly don't think they could handle opening up Access and setting the macro security even if they did. I also found code on the Internet that can be run to edit their registries but I don't want to go there! That is how you have to do it and that is what I do with my distributed apps. The setting is for Access itself, not individual files. |
#7
| |||
| |||
|
|
On Mon, 21 Dec 2009 14:57:45 -0600, Rick Brandt rickbrandt2 (AT) hotmail (DOT) com> wrote: That is how you have to do it and that is what I do with my distributed apps. The setting is for Access itself, not individual files. Do what? Modify the registry? |
#8
| |||
| |||
|
|
PW wrote: On Mon, 21 Dec 2009 14:57:45 -0600, Rick Brandt rickbrandt2 (AT) hotmail (DOT) com> wrote: That is how you have to do it and that is what I do with my distributed apps. The setting is for Access itself, not individual files. Do what? Modify the registry? Yes. I either use VBA code or I include a reg file that I execute with the Shell command. |
#9
| |||
| |||
|
|
On Tue, 22 Dec 2009 06:22:26 -0600, Rick Brandt rickbrandt2 (AT) hotmail (DOT) com> wrote: PW wrote: On Mon, 21 Dec 2009 14:57:45 -0600, Rick Brandt rickbrandt2 (AT) hotmail (DOT) com> wrote: That is how you have to do it and that is what I do with my distributed apps. The setting is for Access itself, not individual files. Do what? Modify the registry? Yes. I either use VBA code or I include a reg file that I execute with the Shell command. Sounds scary to me (like I would know how to do that in the first place!). No problems? |
#10
| |||
| |||
|
|
PW wrote: On Tue, 22 Dec 2009 06:22:26 -0600, Rick Brandt rickbrandt2 (AT) hotmail (DOT) com> wrote: PW wrote: On Mon, 21 Dec 2009 14:57:45 -0600, Rick Brandt rickbrandt2 (AT) hotmail (DOT) com> wrote: That is how you have to do it and that is what I do with my distributed apps. The setting is for Access itself, not individual files. Do what? Modify the registry? Yes. I either use VBA code or I include a reg file that I execute with the Shell command. Sounds scary to me (like I would know how to do that in the first place!). No problems? For 2003 I create these three registry entries... [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\A ccess\Security] "Level"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\ Access\Security] "Level"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engi nes] "SandBoxMode"=dword:00000002 I have those is a reg file named Access2003Security_Low.reg that is installed into the same folder as my app and when the app is run for the first time I use WinExec to execute the reg file... WinExec "regedit.exe -s "PathTo\Access2003Security_Low.reg", 0 WinExec requires a separate declaration in a standard module of... Declare Function WinExec Lib "kernel32" (ByVal lpCmdLine As String, ByVal nCmdShow As Long) As Long It's been a while since I set that up, but if I remember correctly this implementation allows for a standard UAC prompt in Vista so that the user can allow the registry change. I have not had anyone report problems with this. Now, I do notify my users that this is happening and that it affects all Access apps not just mine. In my case, 99% of my users use no other Access apps so I am not stepping on anyone else's toes to do this. I was always getting calls about the prompts and prior to this would just walk them through making the change themselves. |
![]() |
| Thread Tools | |
| Display Modes | |
| |