Icon View Incident Report

Serious Serious
Reported By: Roy Lambert [NLH Associates]
Reported On: 3/31/2016
For: Version 2.23 Build 1
# 4374 Locate on Non-Active Index Can Cause #601 Error When Used Right After Failed FindKey

I just wanted to reply to an email from someone with no works address but with a home email address. Something I've done before, No change that I know of to the segment of code that's affected - this is the line

end else if lu.Contacts.Locate('_HomeEMail', tmpEMail, [loCaseInsensitive]) then begin

The column _HomeEMail is a simple "_HomePhone" VARCHAR(25) COLLATE "ANSI_CI", with no triggers etc on it. There are NULLs and textual data in the different rows.

The result is the following error:

ElevateDB Error #601 The table Contacts is corrupt (The index page is empty).


Comments Comments
The problem occurred when a failed FindKey happened on the active index, and then was followed by the Locate (which uses a different index, internally) immediately afterward.


Resolution Resolution
Fixed Problem on 4/24/2016 in version 2.24 build 1


Products Affected Products Affected
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

Image