Hi Fabio,

unless I am using the _tally in the very first line after the command which causes _tally to be changed, I always assign the _tally to a property immediately if I will need the value later. Also it is worth mentioning that _tally is in deed read/write, so you can actually write _tally=myValue.

>I'm a lot surprised that nobody is complained of this choice, that evidently is mistaken.
>
>Naturally in a normal sequential program this does not create problems.
>But enough to use a timer that periodically it manipulates data on a private datasession
>the issue appear immediatelly ( a workaround exists but this not change the issue )
>
>I ask myself (I have not never used this possibility of VFP):
>in an MDLL VFP application we are sure that all it is ok?
>
>

>_tally = 4
>? SET("datasession"),_tally
>WITH CREATEOBJECT("session")
>	? SET("datasession"),_tally
>	_TALLY= 3
>ENDWITH
>? SET("datasession"),_tally
>

>
>Fabio