And that's what I am doing now. So I dont understand what's a big idea to query SQL from VFP? We should use SP anyway and that SP will use new XML syntax.


>>The big thing about the XML datatype is that you can query inside the XML Datatype column using something like xpath.
>>
>>So if you have a SQL Server XML Column, you can query that column in order to get only certain type of elements or attributes from the XML in there.
>>
>>If the result of that query will map to a Character/Memo Field in the VFP Cursor then we can say it is very useful.
>>
>>Am I correct Ken ?
>
>The query mechanism you are referring to is XQuery which is a superset of XPath (XPath plus more), and that functionality will be built into the .NET Framework 2.0 included with Whidbey and Yukon. If you had a Yukon XML data type map to a VFP cusrsor char memo field, you would not be able to use XQuery to query the XML like you will be able to with Yukon, but you could have a UDF in a VFP SELECT statement that parsed the XML and used XPath but the performance would not be good. The best solution for Yukon XML data types with VFP is to use a stored procedure that executed the SELECT with the XQuery on the server side and then returned the results to VFP in a cursor.