Subject | IBO/4.8.7 |
---|---|
Author | Aage Johansen |
Post date | 2007-10-04T19:28:15Z |
I've just installed IBO/4.8.7 into a new installation of Delphi/6
(yes, I know, I'll move on shortly).
I have this code filling a TIB_Grid:
SQL.Clear;
SQL.Add('select S.DiagnoseDato+0 as invisible, M.* '+
'from MELDING M left join SYKDOMSTILFELLE S '+
' on M.SykdomstilfelleNr = S.SykdomstilfelleNr '+
'where M.PersonLoepeNr = :PNR '+
'order by 1, M.SykdomstilfelleNr, M.MeldingsNr');
KeyRelation:='M';
Later (depending on the user's choice), the grid cursor is moved to
an "interesting" record by something like this:
Locate('M.SykdomstilfelleNr',SNR,[]);
This works nicely, _except_ when the locate doesn't find any record.
The error message is:
---------------------------------
ISC ERROR CODE:335544569
ISC ERROR MESSAGE
SQL error code = -204
Ambiguous field name between table MELDING and table SYKDOMSTILFELLE
SYKDOMSTILFELLENR
---------------------------------
Previously - with an older version of IBO (maybe 4.6) - this worked
fine, always. Apart from using 4.8.7 the only new code is
"KeyRelation:='M';" which up to now wasn't necessary.
Current workaround: trap the exception, and hide it from the user.
The error message itself doesn't look like a perfect hit, does it?
--
Aage J.
(yes, I know, I'll move on shortly).
I have this code filling a TIB_Grid:
SQL.Clear;
SQL.Add('select S.DiagnoseDato+0 as invisible, M.* '+
'from MELDING M left join SYKDOMSTILFELLE S '+
' on M.SykdomstilfelleNr = S.SykdomstilfelleNr '+
'where M.PersonLoepeNr = :PNR '+
'order by 1, M.SykdomstilfelleNr, M.MeldingsNr');
KeyRelation:='M';
Later (depending on the user's choice), the grid cursor is moved to
an "interesting" record by something like this:
Locate('M.SykdomstilfelleNr',SNR,[]);
This works nicely, _except_ when the locate doesn't find any record.
The error message is:
---------------------------------
ISC ERROR CODE:335544569
ISC ERROR MESSAGE
SQL error code = -204
Ambiguous field name between table MELDING and table SYKDOMSTILFELLE
SYKDOMSTILFELLENR
---------------------------------
Previously - with an older version of IBO (maybe 4.6) - this worked
fine, always. Apart from using 4.8.7 the only new code is
"KeyRelation:='M';" which up to now wasn't necessary.
Current workaround: trap the exception, and hide it from the user.
The error message itself doesn't look like a perfect hit, does it?
--
Aage J.