Oh :)
Because when I use the current tag to do serveral actions, sometimes I encounter record out of range, and some other errors, I know this can be prevented by other methods but I just create more tags for different actions... are there any disadvantage to do so? I may change the code asap if there's some hidden risk..

jimi

>TableUpdate() but I asked why you need it :) Generally the current one would serve you well.
>Cetin
>
>>Cetin,
>>oh yes! because I'm modifying a program written by another programmer, he used buffering to allow "cancel" of certain data input from users.. I've just forgot it.. *blush*
>>
>>Hilmar,
>>Thanks! should I just use TableUpdate() before I create the second alias?
>>
>>Jimi
>>
>>>>hi,
>>>>

>>>>use MyTable in 0 order tag MyTag shared
>>>>select MyTable
>>>>seek MyTarget
>>>>replace MyData with NewData
>>>>wait window transform(MyData)  && here it displays the new value, good.
>>>>
>>>>use MyTable again in 0 alias MyTable2 tag MyTag shared
>>>>select MyTable2
>>>>seek MyTarget
>>>>wait window transform(MyData)  && here it displays the old value! eek!
>>>>

>>>>
>>>>why? and how should I do? I do not want to close the table and open it again, because there are serveral grids and relations set up.. or is it necessary to?
>>>>
>>>>Thanks for any help!
>>>>Jimi
>>>
>>>Jimi,
>>>Buffering is in effect. Why would you need to do this ? To use a different tag ? If so you don't need to switch tags nor specify one on open.
>>>Cetin