Yeah, in VFP3 I got away with (inadvertantly) not putting the ";" at the end of a line of LOCAL declarations, when the list went onto a new line. When I converted the project to VFP7 I couldn't believe the number of syntax errors I got (and had got away with), all over the place, in different forms. Syntax checking has been tightened up between the 2 versions.

Terry

>Hi Agnes
>
>Nice catch. However, I would not rely on it being 'fixed' by MSFT. One of the things that have changed in the last versions of VFP is the checking for correct syntax. Also I think the comma makes it more readable.
>
>>Hi,
>>
>>looking in some year old code I found that that REPLACE is not working as expected or documented. It seems not to be harmfull.
>>
>>
>>Help states:
>>REPLACE FieldName1 WITH eExpression1 [ADDITIVE]
>> [, FieldName2
>>
>>What I have found is that the comma is optional. The original statement was like:
>>

>>REPLACE;
>> Field1 WITH Value1;
>> Field2 WITH Value2
>>

>>
>>Testing around I found that
>>

>>REPLACE Field1 WITH Value1 Field2 WITH Value2
>>

>>is working fine too.
>>
>>The first example works at least since VFP 6.0 all the line up.
>>
>>Agnes