Practical Uses of the File Editor

There are many ways to use dbReview, but the following projects are the most likely:

Modifying non-critical data

dbReview is especially helpful when making changes to non-critical data quickly.  Misspelled names, added characters, etc. may be  quickly changed with the editor.  Because it does check the indexes, changes do not require any other activity in the main ASW program.

*** SPECIAL CAUTION ***  When editing records, it is important to know what effect your changes may have.  If a license is changed in the vehicle file, using dbReview, it will not be possible to obtain histories because the license is a key value on workorders. If amounts are changed on the A/R transactions, corresponding changes must be made to the G/L transactions, and perhaps the customer totals.  Otherwise, the figures will not be in balance.

Deleting ancient records

Sometimes records need to be removed, and they may be missing the essential data to handle the task automatically.  As a result, they can be taken out by browsing the file, and marking them for deletion.  Finally, the file should be packed.  Typically, these records occur when someone turns off a machine at the improper time, or aborts an operation at a critical point.

Be sure that you find the related data in all files, or the deletion will not be complete.  To attain space efficiency, the system will maintain records in specialized files.  Work in progress, for example, may be scattered across 8 files.  Although seemingly complex, this is actually more efficient, and eliminates the storage of blank space.

Reviewing special data

In some cases, there may be information in a file that is not normally included in a report, but which you may wish to review.   Some fields are used strictly for connecting records, or joining files, or monitoring status.  In such cases, all data fields are  available for review by the operator.  Most review of data will be done in browse mode.  However, when browsing a file, it may be desirable to look at an entire record.

Custom grouping of data

Sometimes it is nice to look at certain information, selected by group.  For example, you may wish to browse the part numbers, cost, and charge for parts on a range of workorders.  Use the filter command to set the range of workorders, and use the field selection capability  to set the fields to be viewed.  With these filters in place, the operator can scan just the data desired.

Checking for file contamination

In your data files, all information shown should be in the letters and numbers that can be typed at the keyboard.  When files get   contaminated, they often include garbage data, which is shown as "extended ASCII" files.  The only exception are a few files that are encrypted, ie. the password file.  In such cases, the entire file will look strange.

If your file contains a group of records with nonsense data, ie. the extended ASCII set, you may wish to mark the individual records for deletion, and then pack the file.  This will rebuild the data file without the offending, and possibly harmful, data.  Because these characters often contain special printer codes, or computer directives, they can often foul reports and displays.  Eliminating them helps.

If the records can not be marked for deletion, and packed (ie. the system fights you and doesn't work as planned) the file should be checked immediately with dSalvage.  Follow the directions included with that package to perform a fix on the file.