|
Summary:
| |
Can SOL Tracker be run with
Access 2003? |
Details:
| |
Starting with
Build 41 of version 4.0, SOL Tracker is compatible with Access 2003 and will
run on that platform, as well as Access XP (2002). All known
differences between the two platforms have been accommodated for in the
software, except for one. Access 2003 will lock up when SOL Tracker
attempts to check for an updated version of the software through the
AutoUpdates featrue. In order to use SOL Tracker, the AutoUpdates
feature must be turned off, which must be done manually through the Registry
after installing for the first time or after any upgrade to a new build.
Refer to the FAQ question Manually disabling the
AutoUpdate feature through the Windows Registry for the steps to take in
order to do this. It is unknown if the AutoUpdate will work with
Access 2003 when the update files reside on an internal network (versus the
Successline web site).
There is an issue that is specific to Access 2003 related to Macro Security
settings. By default, Access 2003 is installed with a "Moderate" Macro
Security setting enabled. This will result in Access 2003 prompting
the user regarding whether the "unsafe expressions" within the database (SOL
Tracker) should be blocked. If the user chooses to block the unsafe
expressions (selects YES at the prompt), then SOL Tracker will not run
properly.
If the user chooses not to block the unsafe expressions (selects NO at the
prompt), an additional prompt will appear regarding whether the user wishes
to run the database and states that it "may not be safe to open if it
contains expressions that were intended to harm your computer." The
message can be rather cryptic, and makes mention of updating the version of
Jet with Service Pack 8. In reality, the message is just asking
whether the "untrusted" code within SOL Tracker should be run.
Selecting NO at this prompt will prevent SOL Tracker from running.
Selecting YES will cause yet another prompt to appear to confirm that the
user wishes to open the program. The user should select OPEN, or SOL
Tracker will not run.
One way around most of this is to set the Access 2003 Macro Security
settings to "Low". Which will allow untrusted code to run without any
prompts. This can be done by opening Access 2003 directly, and
accessing the Tools menu, then selecting Macros, then
Security, and choosing the "Low" setting. Access 2003 will prompt
regarding whether they wish to block "unsafe expressions". Choose not
to block them, then close Access. Of course, this is against
Microsoft's recommended guidelines, as it will allow any MDB file to run
without prompting the user whether the source can be trusted. If you
do choose to set the Macro Security to "Low", it is strongly recommended
that Anti-Virus software be installed on computers, and user training
regarding not opening attachments received via email is administered.
It is important to mention the the Access XP (2002) Runtime is included on
the SOL Tracker Installation CD, and can be installed on the same computer
simultaneously with the full version of Access 2003. The SOL Tracker
startup routines will actually choose to run on the Access XP Runtime if
both are installed. Doing so will prevent any problems related to the
Access 2003 Macro Security settings. For most users, there is
virtually no difference in program functionality between using the full
version of Access versus the Runtime. |
|
Last Modified: |
March 30, 2004 |
|
Versions Applicable to: |
4.0 |
|
|
