Let’s try this again. (Stupid Outlook…) That’s another possibility. Thanks, Tracy. 😊
The original data source is coming from a SQL backend so I’ve just added some ISNULL calls around the fields which matter to the CURSORTOXML/XMLTOCURSOR calls. -- rk From: ProfoxTech <[email protected]> On Behalf Of Tracy Pearson Sent: Tuesday, March 29, 2022 7:33 PM To: [email protected] Subject: Re: CURSORTOXML and NULLs I tend to create the cursor and use flags to append to the existing cursor. Tracy On March 29, 2022 7:01:47 PM EDT, Richard Kaye <[email protected]<mailto:[email protected]>> wrote: While I'm poking away at this, I thought I'd check with the collective wisdom. I've found a situation where I want to take advantage of CURSORTOXML and XMLTOCURSOR. The issue I'm running into is if the cursor being converted to XML has fields with NULL values in the first record, this appears to affect the resulting XMLTOCURSOR conversion. Any NULL columns will be missing from the result cursor even if later rows in the XML contain values. The hacky workaround seems to be I have to make sure that the first record has non-null values for all columns I want in the cursor. Anyone have any other magic tricks? _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/mn2pr10mb340708d87b1fca04f857069ed2...@mn2pr10mb3407.namprd10.prod.outlook.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
