Hello Don Yeah, that's what I've been doing, sort of. I have a lot of SQL calls to convert to UniQuery by the end of this week (45). For many of them, I can just replace the SQL (used with OLEDB) with the equivalent UniQuery, use the uniXML class to create XML, have it generate a data set and voila, it's good to go. But in some cases the application using these data sets is expecting a specific structure to the data and won't work with the data set produced by default from UniObjects. The most common problem is the logic was written to examine table 0 to determine if any records were returned and to read the records from table 1, but with the way UniData is defaulting the XML, the interesting data is usually in table 1. So my most common work around has been to drop table 0 from the data set, since it usually (in our case) has only the record ID in it. But to do that I have to first drop the relationship to table 1 and the constraint on table1 that it's Id exist in table 0.
Some times that won't work because I do have data in table one that's needed. Then I have the uniXML class populate a temporary data set, and copy the data I want from each table. Complicating this is the problem that the calling application is not documented, so I don't know which of the SQL calls will need to have their data sets modified until I run the application and test it.... (stop me if you've heard this one before).... It's working, but I was hoping I could avoid some of this by managing how UniQuery produced the results to begin with. I have also tried creating an xslt translation to transform the data set in one case. It works fine, but takes too long to program each one. I've read the UniData manual on how to use the mapping file to control how the XML document is formatted, but found it unclear. So I anticipate a long period of trial-and-error figuring out how to make it work. And then, it looks like it will be the same time-consuming process the xslt setup was. I could be wrong about that. But your reply seems to confirm my guess. Thanks again for the reply. Victor St. Clair -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Kibbey Sent: Tuesday, January 17, 2006 5:09 AM To: [email protected] Subject: Re: [U2] XML with UO7.1 I've found it's a lot simpler to just manually create an ADO.NET data structure and then populate it myself with UO.NET. I have to type a little more (perhaps not much more than if I were to use XML) but I get exactly what I want. I have a couple of examples if you'd like to take a look. -- Don Kibbey ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
