for what it's worth - almost ALL my views are of the form:

"Select * from whatever where &vcWhere"

as long as where clause is optimized as normal - rushmore works perfectly and the strategy works great. No problems at all, and it's a lot more flexible than the standard parameterized view.

Filters? bad - bad - bad - we don't need no stinkin' filters!

>>>Does a parameterized CREATE SQL VIEW have to take the form shown
>>>in VFP Help and MSDN Library:
>>>
>>>Value = "Value"
>>>CREATE SQL VIEW lvTable ;
>>> AS SELECT Fields ;
>>> FROM Table ;
>>> WHERE Field = ?Value
>>>
>>>or can it be in this form:
>>>
>>>Condition = "Field = 'Value'"
>>>CREATE SQL VIEW lvTable ;
>>> AS SELECT Field1, Field2 ;
>>> FROM Table ;
>>> WHERE ?Condition
>>
>>No, the view will not work this way.
>
>

Darn.  What's the best alternative?  Would you suggest:
>
>[build m.Condition]
>CREATE SQL VIEW lvTable ;
>    AS SELECT t1.*, t2.Descript, t3.Name ;
>    FROM Table t1, Codes t2, Names t3 ;
>    WHERE t2.ID = t1.CodeID AND t3.ID = t1.NameID
>SET FILTER TO &Condition
>
>Thanks,
>Rich.

Ken B. Matson 
GCom2 Solutions