May 27, 2009 at 3:23 pm
I have a report that needs a new field added to it. That's easy, just refresh the dataset and off you go... Only the field is xml, but not really Here's what I thought that it was....
.... see attachment "Code 1"
Only it could be this bad....
.... see attachment "Code 2"
Or it could have radio buttons, or it could have multiple form tags. Great!
So, the vb.net app parses it this way.... (just adds and extra tag to assure structure)
.... see attachment "Code 3"
Can I just convert this function to return a string and add it to the Code section of the report? Or
should I try to construct the schema and parse it via SQL? Here's what I thought would work as it
works fine for the simple case....
.... see attachment "Code 4"
Any bright ideas out there?
Sorry about the attachment, at least I got it all in one file! ....
May 28, 2009 at 3:30 pm
After wrestling with this issue for several hours, I solved it by moving the vb.net function into the report's code property and adding the system.xml to the assembly references. Hope that helps if anyone else needs to do strange parsing in the future. :angry::crazy::-D
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply