If the where clause is simple enough, that will work, but there is a limit to how complicated it can be and still be able to spcify it in the view designer.

If it gets to the point that the view designer can't be used, I guess the GenDBC method is used to create the views? If I go that route, can I use Unions in my SQL?

Thanks,

June

>June,
>
>One way would be to use a logical parameter that indicates which comparison you want to use (.t. = field1, .f. = field2) and code your WHERE clause appropriately.
>
>HTH
>
>-Dan
>
>>If I've got a parameterized view where sometimes I want to use field1 as the comparison for the parameter, and sometimes I want to use field2 (with a different value for the parameter), how do I do this with MM? Do I have to create two views, identical except for the filter tab, or is there some other way? Is there a way to use views created at run time with MM?
>>
>>Thanks,
>>
>>June