Yes, the August 2003 issue of FoxPro Advisor has a good writeup about using macro substitution with views, starting on page 42.

One additional point that they bring out; don't use VFP's View Designer for views that use macro substitution. Even the improved View Designer of VFP 8 does not save the view correctly. You must define the view in code.

To make sure the parameter is out of scope, you can RELEASE it just before creating the view:

RELEASE lcMacro
DROP VIEW Tralala 
CREATE SQL VIEW Tralala AS ...

>The solution is
>

>CREATE SQL VIEW Tralala AS SELECT * FROM somwhere &lcMacro
>

>without the &? thing.
>
>lcMacro must not be in scope in the moment of view declaration. I've changed all my views this moment, it runs perfectly in VFP 8.0 as well as in VFP 7.0
>