Closed RichardKelters closed 2 years ago
In DataDiggerLib.p the function isIndexActive is incorrect. Possible solution:
`FUNCTION isIndexActive RETURNS LOGICAL ( pcFile AS CHARACTER, pcIndex AS CHARACTER ):
/* See also
https://knowledgebase.progress.com/articles/Knowledge/abl-procedure-fails-to-find-inactive-index */ FIND _file WHERE _file._file-name = pcFile NO-ERROR. FIND _index WHERE _index._file-recid = RECID(_file) AND _index._index-name = pcIndex NO-ERROR. IF NOT AVAILABLE _index THEN RETURN NO.
&IF PROVERSION >= "11" &THEN FIND _StorageObject WHERE _StorageObject._db-recid = _file._db-recid AND _StorageObject._object-type = 2 / index / AND _StorageObject._object-number = _index._idx-num NO-ERROR.
IF NOT AVAILABLE _StorageObject THEN RETURN NO. IF _StorageObject._Object-state = 1 THEN RETURN NO. / 0 = activated 1 = not / &ELSE IF NOT _index._active THEN RETURN NO. &ENDIF
RETURN YES.
END FUNCTION. / isIndexActive / `
With latest change index is wrongly shown as inactive.