Yup, I tested it too. There were no errors. I don't know what the VFP team has changed, but in the past I remember getting problems if there weren't spaces where they belonged. The rule I remember was "code the command as if it were all on one line"
>The following, without indents, works on my computer (VFP6):
>
>
>select;
>artcode;
>from;
>articlemain
>
>
>although, according to your comment, it should give an error.
>
>I think the people at MS simply corrected the problem (say, by adding a space when joining lines), and forgot to remove the warning from the manual.
>
>Hilmar.
>
>>The problem with the semi colon is that VFP puts the line back together when it compiles, so if you have something like:
>>
>>
>>SELECT Field1,;
>>Field2;
>>FROM;
>>MyTable
>>
>>
>>you'll get errors because there are no spaces where they belong. If you indent the additional lines, you won't have a problem. This has always been the case. They're just providing a warning about it in VFP7.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer