Yes, I realize that. But when you do it in a query <CFQUERY NAME="thequery" ....> .... FOR XML ... </CFQUERY>
<cfdump var="thequery"/> the xml is broken into query rows that have nothing to do with the xml at all - at least for us - could be the JDBC driver. Rob -----Original Message----- From: Samuel R. Neff [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 1:03 PM To: CF-Talk Subject: RE: CF 2 XML MSSQL supports two types of FOR XML, FOR XML AUTO and FOR XML EXPLICIT. AUTO creates some default XML. EXPLICIT can be used to create any XML and can be used to make it match a pre-determined schema. At 12:46 PM 1/8/2003, you wrote: >It does; however, the query results are a bit odd (at least they were for >us - the way the "rows" were broken up). So after you do a query with the >FOR XML, you might want to do a cfdump before trying to process the xml >(meaning <cfdump var="#query#"/>). > >Rob ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
