>Sure, if you use cursors. But a lot of people are moving toward objects - ADO Recordsets. Look, it does not take a lot of effort to find a way to employ a new features. Certainly, you can use VFP to scan a cursor and generate XML. Not a damn thing wrong with that. My point is that the IN clause, when you get down to it, is not all that significant.

No, I do not see great advantages to the IN clause, but it is a minor enhancement to the middle-tier. And not to steal Mike's thunder, but following up with the XML argument, VFP 7 will have the CURSORTOXML method. And one of your arguments was the new features of VFP 7 do not seem to address the middle-tier:

>I suppose that is that heart of it. If you are writing classic-style VFP apps, you should be happy now. But what about folks that want to concentrate in the middle and back-end. The area VS.Net appears to be addressing with the new data and application models. When you talk about new features, it appears to me the new VFP 7 really does not address that.

And I know your position on remote views, but I can use them to get data from SQL Server 7 (which as far as I know does not have native XML capability), use VFP 7's CURSORTOXML() function, and deliver XML data to my client. Of course, I will probably continue to use Rick's class just because I trust it. *g*

I have been long-winded here, but I think there are some enhancements to VFP 7 in regard to the middle-tier.