Icon View Incident Report

Serious Serious
Reported By: Krisztian Kepes
Reported On: 8/3/2010
For: Version 2.03 Build 18
# 3266 A Failed Lookup Call Causing Subsequent Locate Calls to Improperly Fail

When I open TableA, it contains lookups into TableB, some of which don't find a matching record. When I then open TableB and try to perform a Locate, it fails even though the record does exist.

procedure TForm1.FormCreate(Sender: TObject);
begin
    with Session do
       begin
       LoginUser:='Administrator';
       LoginPassword:='EDBDefault';
       Open;
       end;
    EDBDatabase1.Open;
    User.Open;
    User.Locate('user','zkocsis',[]);
    User.Close;
    User.Open;
    User.Lookup('kod',NULL,'nev');
    User.Locate('user','zkocsis',[]);  // Fails
end;



Comments Comments
This issue was introduced by the fix for incident #3256


Resolution Resolution
Fixed Problem on 8/5/2010 in version 2.03 build 19


Products Affected Products Affected
ElevateDB Additional Software and Utilities
ElevateDB LCL Standard with Source
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

Image