>>>>I admit I'm a laggard here, not using p-views. Each query, in the case in point, might refer to different source tables with wildly different search conditions. You can set up a p-view using &sqlstr though can't you?
>>>
>>>You can try. I didn't :)
>>>
>>>Actually, trying that animal out may solve some mysteries on the issue of views - like "is the SQL string of a view re-evaluated each time or is it stored compiled" and "if compiled, does an embedded macro force re-evaluation at requery"...
>>
>>One question you may know the (best) answer to ....
>>You can't macro substitute a form property (&thisform.myprop), so if you store an SQL fragment with the intent of using it in a view with an & in it how do you scope the variable?
>
>I store each variable in a form property and use a method which puts the form properties into variables with the correct names before I requery the view.

Hi Barbara,
I understand. Is there more than once place in code where a requery() might take place though? Might need to be a little careful that it's set properly in each case. Or, is there some code location that will always get executed in a requery event ?