Fluke 754 DPC TRACK _ Руководство по эксплуатации онлайн [15/176] 192918

Fluke 754 DPC TRACK _ Руководство по эксплуатации онлайн [15/176] 192918
Overview
The Fundamentals
1
1-5
Table 1-1. Simple Test Results Database
Tag ID
Test
Date
Final
Status
Tester Comments
TT-100 12-1-94 Passed Bob The valve...
TT-200 12-7-94 Passed Elizabeth I noticed...
PT-101 8-4-93 Failed Hank
It follows then that a record is a collection of fields related through some common
element, such as the Tag ID field. This common element is referred to as the
primary field. Thus, a database is a collection of records, and a record is a
collection of fields that are tied together through a primary field. Fields contain
data such as dates, numbers, and text. (Information on the different field types and
rules for data entry is presented in Chapter 7, “Changing Data.”)
Table 1-1 shows five fields comprising a given Test Results record. But what
about the tolerance, the number of testpoints, the input range, etc.? These and
other fields should also be included in the Test Results database, and indeed they
are. Table 1-1 represents summary information only, as you might like to include
in a summary report. The point is this: when you are viewing fields for a given
record, there may be other fields comprising that record that are currently not
visible. So, what dictates which fields are displayed for a given record?
All database programs provide some way of viewing your data. Within
DPC/TRACK, data is presented on forms containing tabs. The form name
describes the type of information found on the form. When a tab is selected (such
as Setup), data relative to that topic becomes visible on what is referred to as the
“page” for that tab. We may access other pages of information by selecting the
various tabs on a given form. One of the nicest features of DPC/TRACK is the
“random walk” whereby you may easily jump across different levels from any
starting point. For example, you may jump between test setup information and
Tag ID history just by clicking on the appropriate tab.
Also worth noting is the use of the term “screen” within the Windows
environment. Typically, Windows applications use screens (windows) as the
primary user interface to the program itself. These screens usually have some
name at the top that identifies what the screen is displaying. For example, when
you start the Notepad program, the subsequent screen displays the name
“Notepad”. When you open a particular text file within Notepad, the screen name
changes to “Notepad - FILENAME.TXT”. Extending the Notepad analogy,
DPC/TRACK displays the name of the form you see on the screen, such as
Instrument View. The form name reflects the type of information that is being
displayed. For simplicity, the terms “form,” and “screen” are used interchangeably
within this manual.

Содержание

Скачать