Deleting Test Points from Database
Deleting a test point will remove all associated data from the database. To save this data, results
must first be archived prior to deleting the test point. The following warning message will appear
before a test point is deleted:
• “Deleting this test point will remove all associated data from the database. To save this
data, results must first be archived prior to deleting test point. Do you wish to delete the
test point(s) at this time?” Yes / No.
After the test point has been deleted, any remaining results on the instrument can only be
deleted manually on the device.
When an instrument containing results for a deleted test point is synced to the database, the
following message will appear:
• “Results from test point(s) ‘x’ cannot be downloaded as these test points do not exist in
this database. They may have been previously deleted. Do you wish to delete the
associated data from the ICON instrument at this time?” Yes / No.
• To download these results, the archived database with historical test point information
must first be restored into the software.
Note: Archived database must be from a time prior to test point deletion.
Re-using a deleted test point
Once a test point has been deleted, it can be re-used for another assignment. It is recommended
the deleted test point’s historical data be archived prior to deletion. Results for the deleted test
point must be manually deleted from the ICON instrument prior to syncing.
• Click “New Test Point” from the Test Point Setup menu in the software.
• The test point number will be assigned the maximum value in the list (ex. if last test point
in list is 500, 501 will be the new test point number).
• Click the “Test Point #” cell to highlight the test point number.
• Change to the desired test point number of any deleted test point.
Note: Test point numbers must be unique. There cannot be two test points with the same number.
A warning will appear if attempting to assign an in-use test point number.
Please
see Chapter
24 for more information on database management.
63