×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




That's rude.

And with 4000 plus lines of file def we really need it to all be there. :-)

Thanks!


- Larry

On 8/16/2012 7:56 PM, Barbara Morris wrote:
On 2012/8/16 7:50 PM, Barbara Morris wrote:
...
I'm not sure whether it would handle the extra subfields or redefines
the way you'd want, though.
...
Rrrrr ... the devil is in the details for things like this.

I just tried having an outer subfield that has data that isn't defined
by the inner subfields, and it doesn't get into the generated XML. That
seems like a deal-breaker, unless your extra subfields always completely
define their containing subfields. But I guess figuring out whether
that's true puts you right back to your original problem.

1 rec.
2 s1 PIC X(10).
3 s1a pic X(3).
3 s1b pic X(3).

MOVE "EE1FF2ABCD" TO s1
XML GENERATE XMLRESULT FROM rec

The resulting XML doesn't have "ABCD".

<rec>
<s1>
<s1a>EE1</s1a>
<s1b>FF2</s1b>
</s1>
</rec>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.