Hi Erik,

I was just starting to play with West Wind's version of this class and seem to be experiencing "dangling object" references after calling XMLToObject, etc. Have you had any trouble with object references (local and/or persisted) not being properly released using these methods? I took a quick look at the code and noticed several lo?? object references being returned back to the calling methods, so I don't really know an easy way to make sure these are getting released properly without doing some major surgery on the entire class structure. I didn't notice any manual garbage collection going on anywhere.

Usually, if I need access to an object reference, rather than returning it back from a method I am calling, I persist it in the class (ie .o??) and make sure it is properly released in the destroy if it's VARTYPE = "O". Just wondering if you've addressed some of these issues in your modifications.

Thanks,
- Randy

>I have posted an update to my XML utility class in the files section, with a few new functions.
>
>The class contains several useful XML related functions in addition to the ones defined in wwXML:
>
>XMLTable()
>returns an HTML stream that contains two XML data islands: one representing the data from your cursor, and one XSL stylesheet that will transform the XML DI into an HTML table with DHTML code in the click event of each header that resorts the table according to the clicked header. It also returns a script that does the transformation.
>
>XMLUpdateGram()
>Creates an XML update gram from the current buffered alias. Analogous to VFP 7's XMLUPDATEGRAM function, but this one works correctly :-), and works in VFP6.
>
>SubmitXMLUpdateGram()
>Submits an XML Updategram to a SQL 2000 Server database using an ADO command object, and returns the resulting XML.
>
>ADOXMLToCursor()
>Converts ADO Compliant XML into a VFP Cursor. Replaces the one in wwXML that currently doesn't work.
>
>http://www.levelextreme.com/wconnect/wc.dll?UniversalThread~?2,2,1254