Lucas, the problem is not with aRow, but with aField. See my first message,
please.

[]s
Andrei


2012/9/28 Lucas Franzen <luc@...>

> Andrei,
>
> Am 27.09.2012 19:09, schrieb Andrei Luís:
> > Hi Lucas, thanks for your answer.
> >
> >
> > "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?
>
> I just checked several OnCalculate I do have in my app and the row is
> 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.
>
>
> ------------------------------------
>
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info
> papers,
> keyword-searchable FAQ, community code contributions and more !
> Yahoo! Groups Links
>
>
>
>

[Non-text portions of this message have been removed]