User's Manual

Importing & Exporting

Importing Procedure Data

8-17

Importing Procedure Data

In order to import Procedure records, you must already have an ASCII file that

contains your Procedure data (named PROC_IN.ASC); otherwise, you must create

one. You may create the ASCII file in the same manner as you would an ASCII

file containing Tag ID data, with the exception of field names (see Example 8.4 for

an illustration).

Your ASCII file may contain any or all of the following fields:

Table 8-2. Importable Procedure Database Fields

Adequacy Delta Test Strategy

Procedure Testpoints

Revision Control Wrapup Messages

Setup Messages

For the import to work properly, your ASCII file must meet the following criteria:

• Data is arranged in columns and rows, similar to a spreadsheet. An entry in a

given column and row corresponds to a specific field for a particular

Procedure record. The order of the columns does not matter.

• The first row contains the headers that identify the data listed within each

column.

• The data within a given row defines a single Procedure record (except for the

first row, which contains the headers).

• Each row ends with a carriage return and line feed. (Rows are separated with

an Enter key.)

• Columns are separated by tabs.

• You may insert spaces before and after data for readability, but don’t use tabs

for this purpose as they will be read as column breaks.

Furthermore, the ASCII file must be titled PROC_IN.ASC and be located in the

directory containing your database files. (The directory containing your database

files is specified with the LccPath variable in your DPCTRACK.INI file.)

DPC/TRACK includes a PROC_IN.ASC file containing some sample data so that

you may work through Example 8.6. For future imports, you may modify this file

as needed or create your own using Windows Notepad (or some other method).