Boy, I've really got to go back for a remedial reading class! This is at least the third time in 12 months that I've done this kind of thing.

As for the warning, I guess it's a good thing. I guess most of us indent and some of us leave a space anyway just to make the semicolon as visible as possible.

Thanks Craig,

JimN

>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.
>
>PACK, RECALL, CALCULATE, SET FILTER and BLANK now support specifying the workarea or table alias by using the IN clause. For example
>
>

>PACK IN MyTable
>

>
>
>>I've read quite a bit of the new VFP 7 documentation referred to here a while back.
>>
>>I must say that the new format looks like it's going to be much much more user-friendly than the old stuff was! In a way it looks like they took a few queues from Hacker's.
>>
>>I saw that CALCULATE, PACK and RECALL are noted as changed, but for the life of me I can't see any difference from the old write-ups. Can someone say what the new stuff is?
>>
>>Something possibly dreadfully dangerous to backward compatibility caught my eye. Deep into the SQL-Select write-up is a simple statement:
>>
>> " Note Be sure to include the space immediately preceding each semicolon. Otherwise, you'll receive an error. "
>>
>>I've gotta believe that beta testers can confirm/deny this.
>>
>>Answers??
>>
>>JimN