AREV Reports Field not a Valid Index (AREV Specific)
At 22 MAY 2002 08:51:45PM Tony Burke wrote:
In an AREV 2.12 system I have defined three fields within a file as BTREE indexes. During the execution of the application a subroutine is locating a record (through a READ via the indexed field) and AREV reports that the field name is not a valid index name. I've tried manually removing and then rebuilding the indexes but to no avail.
Any sugesstions on what else to try?
Thanks
At 23 MAY 2002 01:25AM Tony Burke wrote:
Additional Information:
Right before the message that says 'fieldname xxx is Not a Valid Index Name' a message box briefly pops up and says 'Searching Cross Reference'. I don't ever recall any index as being of type CrossRef.
At 23 MAY 2002 02:30PM Don Miller - C3 Inc. wrote:
A couple of things to check:
1. Do you have any dict field that ends in XREF? If so, the indexing for the file can get really confused. You can check the
!file .. *INDEXES record to see what AREV thinks is indexed.
2. Make sure that your indexes are valid for the data type .. if you are indexing Right-Justified Numeric data and the data doesn't conform to this, the B-Tree is likely to be corrupt.
Other than that, I don't know what's happening.
Don Miller
C3 Inc.
At 24 MAY 2002 01:23AM Tony Burke wrote:
Appearantly a symbolic in the primary file was referencing a non-indexed field in another file. After reindexing the field in the secondary file the error message no longer appears. Very interesting.