| |
These are the system
specific instructions for running the AIMS Database Validation Program. Your responses are in bold face. Words in
brackets, [ ], indicate the actual keys on the keyboard to be used. If you have any questions regarding the
installation procedure, or require the update on 3.5” disks, please contact
technical support at (800) 541-2467.
AIMS
Database Validation Program
•
This
program will fix or report minor issues found in AIMS databases.
• The
program may take anywhere from a couple of minutes to a couple of hours to run,
depending on the size of the database.
• Be sure to backup each database before performing
this update.
•
Download Now!
•
Save this file to any location on your hard
drive.
•
Once the file is downloaded, copy DBValid.exe to
any directory on a computer that can
run AIMS.
•
Click
on Start, then Run.
•
In the Open box, type: dir\DbValid.exe (where dir is the directory where you copied the
file into), then click OK.
•
Select the appropriate
database engine (if other than the default), and click
OK.
•
Enter the appropriate ODBC
Data Source Name (Access & SQL Server customers) or Net
Service Name (Oracle customers), if other than the default, and then
click OK.
- The default
database names are:
Access: AIMS Access
Oracle: AIMSDB
SQL Server: AIMS DATABASE
•
A dialog will appear with 6 options, areas for which the
validation program will validate the
data.
You can uncheck any option for the validation not to perform, though we
recommend leaving all options checked.
•
Click on Begin
to start the program.
•
When the program is finished a message will read
‘Completed’, Click on Exit to close
the
program.
The
following files will be created, displaying the issues found in each area.
The
program will have corrected any issues displayed in each respective area.
If you wish to retain this data, these files should be
printed, as they will be deleted the next
time the DbValid program is run.
priority.log
For AIMS DOS to Windows customers only, unlike DOS, AIMS (Windows) no
longer keeps priority information in the same area as the codes, so the DbValid program removes this
unnecessary data.
name.log
No two codes in AIMS are allowed to share the same description
name. If two codes are found with
the same description, the DbValid
program appends a number to one.
code.log
AIMS only allows codes to contain alphanumeric characters and
hyphens. If any other characters are
found, such as the number sign, the code is renamed.
tag.log
If a tag number on a work order doesn’t exist in the equipment table,
the DbValid program changes it to “NOEQU”. If a tag number in a supporting equipment table (life, warranty,
etc.) doesn’t exist in the equipment table, the DbValid program removes the record.
wo.log
If a work order number in the history table doesn’t exist in the work
order table, the DbValid program
changes the history work order number to 0 (making it a note). If a work order number in the time or
material tables doesn’t exist in the work order table, the DbValid program removes the record.
his.log
The tag number and date on a history record should match the tag number
and status date on the corresponding work order record. If they don’t match, the DbValid program makes them match by
copying the correct information from the work order record.
prt.log
When a part number in a material record doesn’t exist in the part
table: if the part name is not empty, the DbValid
program sets part number to blank; if the part name is empty, the DbValid program moves the part number
to part name; if the part number and part name are both empty, the DbValid program sets the part name to “MISC”.
If a part number is found in supporting part tables (cost, transaction,
…) that doesn’t exist in the part table, the DbValid program removes the record.
hiswo.log
All work order records that contain a tag number in AIMS must contain a
history record. The DbValid program
adds any missing history information and logs it in this file.
|