In general, if you need to change settings on the end users computer, you
can do as you suggest and provide instructions.
Ask yourself what others did when they gave you software? How did they solve
this problem for you, and what did you have to do?
The answer in most cases (well at least for the last 20 some years) is that
you either use an installer, or you provide instructions. There really no
other way here. and, I likely not telling you anything you don't know
already.
for a2003, I just always set the macro security to low, and virtually any
and
all nags and security issues went away.
on how to let Access out of sandbox mode so that the db
can programmatically make controls visible or invisible? I
I am not aware there is ANY TYPE of connection between setting the jet data
engine into sand box mode, and that of enabling, or disabling controls on a
form? Are they
related? This is information is 100% new to me and I not sure where you got
such an idea? Sandbox mode of jet should not effect the ability to enable
(or hide) controls on a form, it never did in the past.
I simply again set macro security to low for 2007 and again I not had any
problems.
eg:
Root: HKCU;Subkey:
"Software\Microsoft\Office\12.0\Access\Security";ValueType: dword;
ValueName: "VBAWarnings"; ValueData: "1"
again, for the above, provide instructions, or use an installer.
For 2007, you can setup a trusted location (again, either use instructions,
or
a installer). That looks like:
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security
\Trusted Locations\
Location(x)
AllowSubFolders (REG_DWORD) = 1
Path (REG_SZ) "C:\MyDatabaseFolder\"
With 2007, the package and deployment tools are free, and the installer DOES
have the ability to add registry keys. However, it very difficult to get the
ms-access package wizard to overwrite existing files (and, for your frequent
bug fixes and updates you have to overwrite your front end (by the
way,,,you do have a split system...right?). So, to get around this
limitation,
I simply use a free installer that lets me overwrite existing files (but,
you
better be VERY VERY VERY VERY careful...else you overwrite your customers
data
file!!!).
I been using the free inno installer for years...it works well.
You'll find the inno installer here:
http://www.jrsoftware.org/isinfo.php
Note the above link also has a good number of support and very active
newsgroups that can help you with your install setups also. I highly
recommend this installer, and it is free. and, for questions, check
out the newsgroups there also.
A typical inno script that runs after the download looks like:
[Setup]
SourceDir=c:\Documents and Settings\All Users\Application Data\RidesL
AppName=Rides Reservation System
AppVerName= Rides 2.0
DefaultDirName={commonappdata}\RidesL
DefaultGroupName=Rides
Compression=lzma
SolidCompression=yes
DirExistsWarning=no
DisableDirPage=yes
DisableProgramGroupPage=yes
Uninstallable=no
[Files]
Source: "RidesXP.mde"; DestDir: "{app}"
[Registry]
Root: HKLM;Subkey:
"Software\Microsoft\Office\11.0\Access\Security";ValueType: dword;
ValueName: "Level"; ValueData: "1"
As mentioned, I really don't see the need to change the sandbox mode of jet,
but in 2003, that setting in an inno script is:
Root: HKLM; Subkey: "SOFTWARE\Microsoft\Jet\4.0\Engines"; ValueType: dword;
ValueName: "SandBoxMode"; ValueData: "2"
