No it's not a bug. As you know, you can assign alias to a field in the select. The 'AS' keyword is optionnal in such case. IOW

..., Level4; && Here I missed comma after last field
                      Br1, ... 
* is the same as 
..., Level4 AS  Br1, ... 

>I have mistyped SQL statement
>
>
>

>   SELECT KStr, KDlj, Individ, Level1, Level2, Level3, Level4; && Here I missed comma after last field
>                      Br1, Br2, Br3, Br4, Br5, Br6, Br7, Br8, Br9, Br10, Br11, Br12,;
>                      PlanDlj.Kod AS OldKod, 0000000000 AS NewKod, 0000000000 AS NewStr;
>                      FROM PlanDlj;
>                      LEFT JOIN PlanStr ON PlanDlj.KStr == PlanStr.Kod;
>                      WHERE PlanStr.Scenario == kodSc;
>                      INTO CURSOR cDlj READWRITE
>

>
>The result is All fields are full except Br1. VFP don't raise an error. VFP 8 SP 1.
>
>When I set the comma on the right place everythink is OK.
>So my question is this a BUG or No? ( I think it is)