>Bonjour Fabio,
>
>Thank for help but it work not good.

Not good. Why?

>
>I think that perhaps impossible with One shot command....?????

Possible it is, sure.

>
>

>UPDATE Resident SET NoitelephoneIdReportActif =  0
>
>UPDATE R SET NoitelephoneIdReportActif =  F.ireport ; && CHOICE WHERE AND WHAT TO UPDATE
>      FROM Resident R LEFT JOIN cFiltre F ON F.itelephoneid = R.itelephoneid ; && BUILD THE WORK SET
>   WHERE f.ireport = noreport AND F.itelephoneid = R.itelephoneid   && FILTER THE WORK SET
>
>

>
>
>*-- if the condition is not then replace with 0
>
>UPDATE R SET NoitelephoneIdReportActif = NVL( F.ireport , 0 ) ; && CHOICE WHERE AND WHAT TO UPDATE
> FROM Resident R LEFT JOIN cFiltre F ON F.itelephoneid = R.itelephoneid ; && BUILD THE WORK SET
> WHERE f.ireport = noreport AND F.itelephoneid = R.itelephoneid && FILTER THE WORK SET
>
>
>
>But it do'nt work...
>

Don't work ! Why ?

UPDATE R SET NoitelephoneIdReportActif =  NVL( F.ireport , 0 ) ; 
      FROM Resident R LEFT JOIN cFiltre F ON F.itelephoneid = R.itelephoneid ; && is F.itelephoneid a primary/candidate key ?
    AND f.ireport = m.noreport  && WHAT IS THIS?

>
>
>> CURSORSETPROP("Buffering" ,5,"Resident") && WHY YOU USE A BUFFER ?
>>
>IN foxtalk 2.0 March 2005 Page 15 Tips from the vfp team...
>
>it goes faster ! ( no trigger ).
>
>bernhart

Have you a Resident's trigger ?
If you have a trigger, it fire when you do the TABLEUPDATE(.T.),
then: is the complete operation faster ?
The table buffer overhead slow down the operation by a 4-6X,
then i'm not sure.