hey gerry,
thanks for clarifying this for me. i figured it had to be standard
functionality now i just need to adapt a .xsd.
cheers!
gerry wrote:
> that is the way it works - in the 1st case there is no cue to tell the
> parser that bugs is a row collection as opposed to a single row
> to get the required result use a .xsd schema
>
>
>
> "th3dude" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hey there,
> >
> > I am looping over a dataset created from the "readxml" method and there
> > seems to be a problem when it gets to a node that has just one child
> > for example:
> >
> > This block yields the correct result and is translated as a proper
> > table with columns and rows:
> > <Bugs>
> > <Bug>56</Bug>
> > <Bug>51</Bug>
> > </Bugs>
> >
> > This block just gets treated as a column and no rows.
> >
> > <Bugs>
> > <Bug>56</Bug>
> > </Bugs>
> >
> > Am i missing something or is this a bug in the framework?
> >
> > Seems like they should get treated the same way.
> >
> > Thanks for any insight!
> >
|