>>>Hi,
>>>
>>>Is there a away to change the WHERE expression without
>>>creating the entire view ? (I could not find any)
>>>
>>>I have a Notes form, that need to serve 2 other forms like supplier
>>>and one for distributor. If I use the same view for both forms then I
>>>need to change the filter expression on the fly ?
>>>
>>>I could NOT see away to do it with DBSETPROP() as of now.
>>>
>>>I would need to change the actual field it instead of :
>>>
>>> WHERE Notes.idis_sysid = ?ParentPKValue
>>>
>>>To:
>>>
>>> WHERE Notes.iPub_sysid = ?ParentPKValue
>>>
>>>Thanks
>>>
>>>Doron
>>
>>Personally, I would not do it, but it's doable
>>cWherestring='Notes.iPub_sysid = ?ParentPKValue'
>>create sql view myview as select * from notes where &cWherestring.
>
>Ed, this is going to resolve the macro-expansion at the time of the CREATE SQL VIEW - he'd really have to use WHERE EVAL(wherestring), even uglier as far as performance. He'd be better off creating a new view dynamically, or creating several parameterized views to accomplish this.

Yes, that's why I said that personally I would not do this. I guess it's task for cursor.