Subject | CalculatedField problem with MIDAS |
---|---|
Author | Dominique Van Roie |
Post date | 2001-01-04T17:51:01Z |
Hi,
I found an other problem with IBOQuery caclulated fields when viewed through
a client DataSet.
If you set ClientDataSet.PacketRecords to a positive number like 20, the
caclulated fields are empty
on the clientDataSet side but are ok on the IBOQuery side.
All is ok if ClientDataSet.PacketRecords = -1 but I really prefer the
incremental fetching
I found that the calculated fields values are lost in
procedure TDataSetProvider.InternalGetRecords
...
DataSet.BlockReadSize := Count; // count is the
ClientDataSet.PacketRecords
...
end;
As an attachment is a small .dpr reproducing the problem.
You will have to adapt the path to employee.gdb (demo file comming with
delphi)
<<CalcFieldsBug.zip>>
I made all my testing with the latest version of IBO : IBO_3_6_Cc.zip
Does anybody know a fix or a workAround
Thanks
Dominique
[Non-text portions of this message have been removed]
I found an other problem with IBOQuery caclulated fields when viewed through
a client DataSet.
If you set ClientDataSet.PacketRecords to a positive number like 20, the
caclulated fields are empty
on the clientDataSet side but are ok on the IBOQuery side.
All is ok if ClientDataSet.PacketRecords = -1 but I really prefer the
incremental fetching
I found that the calculated fields values are lost in
procedure TDataSetProvider.InternalGetRecords
...
DataSet.BlockReadSize := Count; // count is the
ClientDataSet.PacketRecords
...
end;
As an attachment is a small .dpr reproducing the problem.
You will have to adapt the path to employee.gdb (demo file comming with
delphi)
<<CalcFieldsBug.zip>>
I made all my testing with the latest version of IBO : IBO_3_6_Cc.zip
Does anybody know a fix or a workAround
Thanks
Dominique
[Non-text portions of this message have been removed]