<div class="gmail_quote">On Fri, Jul 1, 2011 at 10:09 AM, Chris Nighswonger <span dir="ltr"><<a href="mailto:cnighswonger@foundations.edu">cnighswonger@foundations.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
<div class="gmail_quote">On Fri, Jul 1, 2011 at 9:52 AM, Ian Walls <span dir="ltr"><<a href="mailto:ian.walls@bywatersolutions.com" target="_blank">ian.walls@bywatersolutions.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Unfortunately, that's just the way that ExtractValue works. From the manual:<br><br>If multiple matches are found, the content of the first child
text node of each matching element is returned (in the order
matched) as a single, space-delimited string.
<br></blockquote></div><br></div>The sad thing is if it was comma or otherwise delimited we could do some splitting foo. But spaces will inevitably appear in the date in the specified fields.<br></blockquote><div>
<br>Read 'data' for 'date'.... <br></div></div>