Possible to stop "Unsafe Expression" warnings (Access 2003 and XP)?
in [Help]
|
Prev: Sharepoint security settings for distributing Access 2010 databasesvia Sharepoint 2010
Next: best way to handle #ERROR in Query
From: PW on 21 Dec 2009 19:11 On Mon, 21 Dec 2009 14:57:45 -0600, Rick Brandt <rickbrandt2(a)hotmail.com> wrote: >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. Do what? Modify the registry? -pw
From: Rick Brandt on 22 Dec 2009 07:22 PW wrote: > On Mon, 21 Dec 2009 14:57:45 -0600, Rick Brandt > <rickbrandt2(a)hotmail.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.
From: PW on 22 Dec 2009 14:11 On Tue, 22 Dec 2009 06:22:26 -0600, Rick Brandt <rickbrandt2(a)hotmail.com> wrote: >PW wrote: >> On Mon, 21 Dec 2009 14:57:45 -0600, Rick Brandt >> <rickbrandt2(a)hotmail.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? Thanks Rick
From: Rick Brandt on 22 Dec 2009 18:30 PW wrote: > On Tue, 22 Dec 2009 06:22:26 -0600, Rick Brandt > <rickbrandt2(a)hotmail.com> wrote: > >>PW wrote: >>> On Mon, 21 Dec 2009 14:57:45 -0600, Rick Brandt >>> <rickbrandt2(a)hotmail.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\Access\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\Engines] "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.
From: PW on 22 Dec 2009 19:11
On Tue, 22 Dec 2009 17:30:01 -0600, Rick Brandt <rickbrandt2(a)hotmail.com> wrote: >PW wrote: > >> On Tue, 22 Dec 2009 06:22:26 -0600, Rick Brandt >> <rickbrandt2(a)hotmail.com> wrote: >> >>>PW wrote: >>>> On Mon, 21 Dec 2009 14:57:45 -0600, Rick Brandt >>>> <rickbrandt2(a)hotmail.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\Access\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\Engines] >"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. > > Thanks Rick! I may give it a go. -paul |