Ed,

>>
>>Yes, we're using this technique. But if our where expression would be extremely large? How can we operate in this case? And if we have in where clause something like street="Beacon st."? We can not use a space as a delimiter, we should use more clever approach, that's why I said, it's too bad, MS limited macro command...
>>
>
>If you're using VFP6 SP3, and the statement is excessively larger, you could create a UDF() on the fly to evaluate the WHERE condition, compile it on the spot, and use the UDF in your WHERE clause.

Yes, I believe, we're using VFP6 SP3.

I'm afraid, it's too difficult. And also I know, that UDFs in SQL could
1) slow down the speed
2) work unpredictable (it could work in one situation and not work in another).

We have to find simpler solution. On Monday will be our programmer's meeting, so we'll discuss.
I think, it's a general situation, so, if you already have a working example and can share with us, it would be great.

BTW, I ask about VFP7.0. Do you know, when will MS release this product? Will this annoying limitation be fixed in the new version?

I can write a long list of desired improvements in VFP (actually, I did it once). Should I? And where do I need to post it? In chatter section?