VALDOCS 1.1X TIPS

Avoiding the corrupted Index

Normally when the Indexer goes bad ("Error on reading disk = 1:)
you have approximately a 99.5% chance that you will be able to
recover everything on your disk.  But because there is a slight
chance that all your data on the disk could be lost, we have
provided a couple of suggestions to help avoid this.

1.   ALWAYS, use the <M>iscellaneous menu to change data
     diskettes.  If you change a diskette without telling Valdocs
     1.1x that you have done so, it does not know that it must
     find the new diskette's Indexer files before they can be
     used.  Instead it assumes that the Indexer data files are in
     the same location on the new diskette as they were on the
     old one.  Then when a document is STOREd, it saves the
     Indexer data on the new diskette at the location where it
     thinks it should be and whatever data may have been there is
     gone and the new Indexer file is now corrupted.

2.   It seems that when you delete a file from an Index, the
     Indexer does not always process the deletion correctly,
     which can set you up for this error, also.  If a deletion is
     not processed correctly, the next time a document is STOREd
     to the Index, it may end up corrupting the Indexer data
     files.  Unfortunately, there is no way to tell when a
     deletion did not take, so the best way to avoid this is by
     not deleting files from the Index.