Sandbox mode ?

[paddymx]

I recently tested an app w/runtime included on a machine that didn't have Office . Of course the app wouldn't work because of the Sandbox. As the machine didn't have office, no way to change macro security setting. I see in the setup package wizard (vstool, developer extentions 2003) that I can change/add a key:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engi nes] SandBoxMode DWORD:= 00000000 which completely disables sandbox. At first blush this might be considered foolish, but, as the DB is a MDE, I would think it highly un likely that it could be compromised. In fact, if someone had the knowledge to hack the mde, would they not also be able to hack sandbox? What difference would sandbox make. Looking for thoughts/opinions or possible alternatives.

TNX

[ItsMe]

I believe changing that registry key will be the same as adjusting the slider in the "Macro Security" GUI. So creating a key to disable sandbox mode will be the same as adjusting the macro settings to low.
http://office.microsoft.com/en-us/ac...001050432.aspx
and
http://office.microsoft.com/en-us/ac...in=HP001050432

The alternative would be to use a newer version of Access and adjust the trusted locations settings. This way, only specific directories on a network or on a local machine will have the privileges.

[paddymx]

I believe changing that registry key will be the same as adjusting the slider in the "Macro Security" GUI. So creating a key to disable sandbox mode will be the same as adjusting the macro settings to low.
http://office.microsoft.com/en-us/ac...001050432.aspx
and
http://office.microsoft.com/en-us/ac...in=HP001050432

The alternative would be to use a newer version of Access and adjust the trusted locations settings. This way, only specific directories on a network or on a local machine will have the privileges.

Thanks, I've read both those and came to the same conclusion. A newer version is out of the question as I am on a fixed income and I will/would be giving this away at no cost.

[ItsMe]

I suspected as much but I believe these are the options. So, might as well list them all out here and mention creating a certificate. Buying a cert is money and, if I recall correctly, creating a single use cert on the machine will require full install of Access.

So modifying the registry sounds appropriate to me. Good Luck!