| Subject | Re: [IBO] Calculated Fields - still didn´t go t them |
|---|---|
| Author | Lucas Franzen |
| Post date | 2012-09-28T08:30:13Z |
Andrei,
Am 27.09.2012 19:09, schrieb Andrei Luís:
not null.
If I have defined two calculated fields it will be called twice (for
each record that's retrieved).
It is NOT called if the query is empty, so aRow is not null.
Did you try to clear the Query and start from scratch?
Sometimes it happens that you have settings you don't see which are
causing the problem.
Luc.
Am 27.09.2012 19:09, schrieb Andrei Luís:
> Hi Lucas, thanks for your answer.I just checked several OnCalculate I do have in my app and the row is
>
>
> "In which code AField was NIL? In the one above?"
>
> Yes, the procedure CalculateFields is always receiving Afield = nil, so any
> call to this variable raises an access violation. What is wrong?
not null.
If I have defined two calculated fields it will be called twice (for
each record that's retrieved).
It is NOT called if the query is empty, so aRow is not null.
Did you try to clear the Query and start from scratch?
Sometimes it happens that you have settings you don't see which are
causing the problem.
Luc.