third_party_content:community:commentary:forums_nonworks:d6f177e69d96473485256817000e7749

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 26 OCT 1999 10:38:00PM Sainimili Saunalia wrote:

Have been running into an indexing error. Running Arev 2.11 and trying to view a list of index in a file. A message appears saying

" The !referencefile file is not available"

Is there a way I can access this shriek file - or index file.

In the files with index, the related files column shows

" Error: No !referencefile"

When being listed, all the index fields still appear.

Is there a way that I can still access the shriek or index file. All signs show that it is there but I cannot access it.

Cheers


At 27 OCT 1999 09:46AM Don Miller - C3 Inc. wrote:

I have seen this happen when the Index (the !filename) is corrupted. Usually it is the *INDEXES record. You might try removing the index from the file. Next, do a setfile to the !filename and clear it. You should be able to delete it and then re-create the indexes. Make sure you backup your files first!!!

Don Miller

C3 Inc.


At 27 OCT 1999 01:01PM Victor Engel wrote:

Arev uses volume labels to keep track of volumes since they can be referenced several ways. This is used in order to keep you from attaching files on the same volume in more than one way, for example using a volume pointer in the VOC file or via a relative directory name or via an explicit directory path.

The volume label is stored in the REVMEDIA record in the REVMEDIA file for that volume.

Indexes are managed using these same labels. Both the !filename record and the ! record of the !filename file contain references to the volume label. If the volume label stored in the !filename or ! record do not match the volume label of the REVMEDIA record in the REVMEDIA file, the error you mentioned will be displayed.

The cause of this happening is usually copying files at a DOS level from one volume to another.

Another potential cause of the error is if there is an inconsistency between the MFS entry in the REVMEDIA file, the index markers on indexed fields, and references to the actual index file.

Since there are so many things to consider, it is usually simplest to manually delete indexing from each field and set them up again. If you cannot access the file at all, though, do the following:

1 Edit the REVMEDIA entry for the file and remove the SI.MFS reference. This will allow you to attach the file without requiring the !filename file to be available. You can still attach the !filename file if it is available, but it will function as a data file, not an index.

2. Reattach the file.

3A. Delete the !filename file and remove and reapply indexing to all the fields, or:

3B. Modify the !filename record of the !filename file to contain the same volume label as the volume that it is on. This is not for the faint of heart. You must know what you are doing here.

4B. Delete the ! record of the !filename file.

5B. Reapply SI.MFS

6B. Reattach the file.

Steps A are simpler, but steps B will keep you from having to rebuild the index, assuming you have a good index.

Caveat: this is all off the top of my head so I might have left something out. Someone please jump in if I missed something.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/d6f177e69d96473485256817000e7749.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1