Hi Both
Not used Tasks yet but just lookig at the code
they are marked [transient] which means that they are not stored
they are [SQLCOMPUTED] so they are exposed through SQL
you can get to them by calling the sql code but use the object syntax
so for
DisplayErrorNumber
the sql is
{DisplayErrorNumber}=$SYSTEM.Task.DisplayErrorCalc({ER},1)
from the object projecttion you can do
write=$SYSTEM.Task.DisplayErrorCalc(..ER,1)
Why do they do this?????
I suspect it's to make the properties ReadOnly
there is a flag in the property inspector "ReadOnly" but this did/does
not work
or at least it did not - it's been a few versions ago when I had a
conversation with support on this
Peter
On Thu, 5 Aug 2004 18:28:01 +0200, "Falko Rotter" <[EMAIL PROTECTED]>
wrote:
>Hi,
>
>i have a problem with the DisplayXXXX-properties of the Task-class.
>If i open an existing task with
>
>do t=##CLASS(%SYSTEM.Task).%OpenID("2")
>write t.DisplayNextScheduled
>
>then i'm getting an empty string for all transient DisplayXXXX-properties.
>Why?
>(via SQL all DisplayXXX-Fields have no empty values)
>
>Best regards,
>Falko
>
