Subject | No exception raised when required fields are not filled |
---|---|
Author | Hianoto Santoso |
Post date | 2002-01-14T01:20:46Z |
Dear all,
I just had a problem now <g>, which there was no exception raised when required
fields are not filled.
The DDL of one table example (actually this problem occurred for all tables):
create domain D_SEA_KODE as char(10) not null;
create domain D_SEA_NAMA as char(20) not null;
create table season(
SEAKODE D_SEA_KODE,
SEANAMA D_SEA_NAMA);
In my Delphi code, it was a base class with action attached to "Save" button:
procedure TfrmBaseDb.btnSaveClick(Sender: TObject);
begin
try
grdTemp.Enabled := True;
dsTemp.DataSet.Post;
trnTemp.CommitRetaining;
modeNavigation;
except
InfoError( 'Duplicated or wrong entry, please recheck your input' );
end;
end;
My application handled this exception properly for weeks, however this problem
appeared just now... and I don't know where to fix it, of course I can browse through
my VCS to trace for changes, however it might take plenty of time which I cannot
afford <g>
I thought it was FB problem, but when I used IBConsole/Marathon to try it (add a new
record, fill the seaKode but skip the seaNama), they can handle it properly.. therefore
I suspect there might be something wrong in my code or components I used, but I
just use IBO and FR...
Please kindly advise what I should check or revise..
Thanks,
Hian
I just had a problem now <g>, which there was no exception raised when required
fields are not filled.
The DDL of one table example (actually this problem occurred for all tables):
create domain D_SEA_KODE as char(10) not null;
create domain D_SEA_NAMA as char(20) not null;
create table season(
SEAKODE D_SEA_KODE,
SEANAMA D_SEA_NAMA);
In my Delphi code, it was a base class with action attached to "Save" button:
procedure TfrmBaseDb.btnSaveClick(Sender: TObject);
begin
try
grdTemp.Enabled := True;
dsTemp.DataSet.Post;
trnTemp.CommitRetaining;
modeNavigation;
except
InfoError( 'Duplicated or wrong entry, please recheck your input' );
end;
end;
My application handled this exception properly for weeks, however this problem
appeared just now... and I don't know where to fix it, of course I can browse through
my VCS to trace for changes, however it might take plenty of time which I cannot
afford <g>
I thought it was FB problem, but when I used IBConsole/Marathon to try it (add a new
record, fill the seaKode but skip the seaNama), they can handle it properly.. therefore
I suspect there might be something wrong in my code or components I used, but I
just use IBO and FR...
Please kindly advise what I should check or revise..
Thanks,
Hian