>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.

I remember spending over half a day on a problem in VFP5. It was as if the line hadn't been written. No warning, nothing. Thought and thought about it. Put in a space before the semi-colon just for grins and everything worked. Up until then I had never put in the space. One of my friends then told me about this oddity. Seems like this bug doesn't always bite. Just once in a while and that's enough.