I Don't beleive it's a bug.

From VFP8 Help:

In prior versions of Visual FoxPro, you could create a new view that contained syntax errors. Visual FoxPro now validates views to ensure no syntax problems exist.

For example, suppose you included a memory variable as part of the view definition. In previous versions, the memory variable did not need to exist when the view was created because Visual FoxPro did not perform syntax checking. Now, the memory variable must exist.


Did you get any bug confirmed by MS? What are the bugs found?


>This is getting depressing. Since the 10 day's or so ive been working with VFP 8 this is the 5th bug I had to report. I wonder what MS definition of stable they use when they say it's the most stable version. It does not crash more often than VFP7 allright, but the other bugs are pretty irritating.
>
>In VFP you can write a SQL VIEW definition with a macro in the where clause like
>
>

>CREATE SQL VIEW MyView AS ;
>     SELECT * FROM MyTable WHERE &?cWhere
>

>
>which enables you to define a flexible whereclause in runtime by just filling the cWhere variable.
>
>However in VFP8 the view cannot be created either in code or the view designer. It would give a nice Syntax Error. The only workarround I found is to create the view in VFP.
>
>To the VFP team: If you're going to fix this please make it also possible for remote views to use this strategy....
>
>I beginning to wonder if I should start a new thread: The 100 bugs in VFP8
>
>Walter,