No ALL is not an option with WHILE. It'd fail unless first key is what you're looing for. I never saw it fail.
Forget UPDATE. I missed FPD25 in title.
Same applies to scan and other commands with a scope. If you want to use ALL option you can do it with set key :

set key to m.id
replace all .... with ...

Cetin


>I am not chnaing the id so in that case is ALL okay. I have this situation where generally this code works and in around 2% of the cases this fails, why I can understand. Does the same apply to SCAN
>
>I have never used UPDATE is it more reliable and fast, that was the reason for SEEK and REPLACE WHILE.
>
>>>Hi All
>>>
>>>I have these lines:
>>>
>>>

SEEK m.id
>>>REPLACE ... WITH ... WHILE dbf.id = m.id

>>>
>>>Is this okay cause at time I have found it to fail. Is the failure my otherwise problem or this command problem. Is ALL required as below?
>>>
>>>

SEEK m.id
>>>REPLACE ALL ... WITH ... WHILE dbf.id = m.id

>>>
>>>Please advise
>>
>>No ALL is not needed. It might fail if you're changing the id field.
>>You can use 'for' in that case or update-sql :
>>
>>REPLACE ... WITH ... FOR dbf.id = m.id
>>
>>or :
>>update myTable set fieldname = value where id = m.id
>>
>>Cetin