|If you need help,
send email to email@example.com.
But before contacting us, please review the following list of problems.
Setup program can't find VBRUN300.DLL when running from NETSET directory.
Setup program can't
read/write PRTRACK.KEY file
Opening PR-Tracker key file when starting PR-Tracker
Property Value while printing a problem report
Problems printing with
HP LaserJet printers
Incompatible database version
Can't Open Project Database
Setup program can't find VBRUN300.DLL when running from NETSETUP
- If the SETUP1.EX_ has a date older than
May 18, 1996 then this error will occur if the VBRUN300.DLL is not already in your Windows
system directory. To work around this problem copy files SETUP.INF and SETUPKIT.DL_ that
came zipped in PRTRACK.ZIP to the NETSETUP directory.
can't read/write PRTRACK.KEY file.
- If SETUP1.EX_ has a date older than March
26, 1996 then it will not be able to read or write to the PRTRACK.KEY file if it is stored
in the root directory. Most users don't encounter this problem until they try to get
PR-Tracker working from the network and they share out the database directory such that it
is on the root directory of a network drive. To fix this problem, if you have version 2.04
replace the SETUP1.EX_ file with the new one. You can download the new SETUP1.EX_ file
If you have a version earlier that 2.04,
download PR-Tracker 2.04 and do an upgrade install.
To workaround this problem without
downloading SETUP1.EX_, don't install PR-Tracker such that the PRTRACK.KEY file is on the
root directory of a network drive.
Error Opening PR-Tracker key file when starting PR-Tracker
- This error occurs if you have become
disconnected from the network drive where PR-Tracker is installed. You may want to edit
the PRTRACK.INI file so that the database_home variable uses a UNC pathname instead of one
that uses a drive letter. For example
Value while printing a problem report
Problems printing with HP LaserJet printers
- A few problems have been reported printing
with HP LaserJet printer using the PCL driver. One of these is that List of Selected
Problems report is only partially printed. To eliminate the problem, install the
postscript driver for the printer and print with it.
- This problem occurs when PR-Tracker users
have different versions of the VBDB300.DLL installed on their workstations. PR-Tracker
ships the VBDB300.DLL dated 4/28/93 and it creates an Access 1.10 database. Newer versions
of the VBDB300.DLL create and Access 2.0 database.
To work around the problem, only create new projects from
workstations containing the DLLs shipped with PR-Tracker. The workstations with the newer
DLLs will still be able to do read/write operations on project databases without changing
the format. If you have already created the project and entered data, use the database
repair utility to rebuild the database on a workstation with the shipped DLLs.
PR-Tracker 2.05 will use the Access 2.0
database format so that this problem will be fixed.
Can't Open Project Database '
- This problem is caused by a corruption of
one the DLLs. Delete the PR-Tracker program and all related DLLs and from your Windows
system directory and reinstall. DO NOT delete the database.
You can determine which DLLs to delete (or rename)
by looking in the NETSETUP directory, which should be where the database is located. The
DLLs that are copied to the Windows system directory are in there and have names *.DL_.
Those are the files you should delete from your Windows system directory before