>You need to check for that checking the XML. THe easiest is by loading the XML into the XMLDOM and checking for the various data keys. if they're not there the request data is empty.
>
>IF the data generated contains a schema (CURSORTOXML schema that is) then the cursor always is created... if not - well you may have problems (see below).
>
>Actually after you mentioned this I tried a few things and found some interesting results. None of them crashed VFP, but some of them have left me scratching my head on what's going on with the schema generation.
>
>

>SELECT * from tt_cust WHERE .F. into CURSOR TQuery
>
>lcXML = ""
>CURSORTOXML("TQuery","lcxml",1,48,0,"0")
>
>?  lcXML  && Empty XML Document - no schema
>
>CLOSE DATA
>
>XMLTOCURSOR(lcXML,"TCustomers")
>
>BROWSE  && Works with new structure????
>

>
>To my surprise this actually worked. I'm not sure how VFP is figuring out how to create the cursor in the code above when the XML is basically empty...

This works locally. Using that code do show an empty cursor. But, when I use the code on my client side, I still have a crash if no cursor is present. I do now generate the XML with the line you gave me. That works. But, on the client side, I still have the same problem. Have you tested from the code I use in this thread?