PR-Tracker stores problem report data in Microsoft Access 2000
format. Importing your data mostly involves creating an Access 2000 file that PR-Tracker can
read. However there are a few additional steps. In order to import data into PR-Tracker,
you first need to know how PR-Tracker stores data. We explain this in the next paragraph.
The data for each PR-Tracker project is stored in is own directory. The project data is
stored in three kinds of files: .CFG, .MDB and .XML files. The .CFG file contains
information about how the project is configured. The .MDB file contains all the problem
report data and its fields must match the specification in the .CFG file. Lastly there is
one .XML file for each problem report in the database. The .XML files are stored in an ASCII readable format and can be viewed with any text editor. Windows Notepad would be one such text editor. Before performing the import steps you may want to inspect the files for the DEMO project that comes with PR-Tracker.
To import the data do these steps:
- Create a new project and configure it as desired. This creates the .CFG file and .MDB
- Put your problem data in the .MDB file created by PR-Tracker. If your problem data is
stored in Microsoft Access or Excel you can probably paste the data into the
Problem Report table of the .MDB file one
column at a time. If your data is not in Microsoft Access it is likely that the program
storing your data can be exported to Access format.
- You will notice a checksum field in Problem Reports table of the PR-Tracker
created database. Set this value to 1. Its proper value will be calculated in
- Create the .XML files. A .XML file is created by PR-Tracker whenever you view a problem report and the .XML file doesn't already exists. The easiest way to create these files is to open the project with PR-Tracker and double-click the first problem in the list to view it. Then from the Problem Report view click the Next menu until you reach the last problem report.
- Run the Database Repair Utility on the imported project. This will rebuild
the .MDB file using the XML files and calculate the proper value for the
checksum field in the Problem Reports table.
If you receive an "Error 94: Invalid use of null" during step
4, do the
Set the "Allow zero length string property" of the Originator field to
- Use the following Access query to replace nulls with the empty strings.
UPDATE [Problem Reports] SET Originator = "" & Originator, Investigator =
"" & Investigator, Resolver = "" & Resolver, Verifier =
"" & Verifier, [Assigned To] = "" & [Assigned To] WHERE
Originator is null OR Investigator is null OR Resolver is null Or Verifier is null Or
[Assigned To] is null;
Bug tracking doesn't have to be complicated | Help | Site Map