Jan,
After analyzing your solution understood that you used the empty lines
as group level record delimiters. I didn't want to use any
pre-processing code to modify my inboud flat-file so based on your
logic to use Infix I created a new schema to just use <CR><LF> as
record level delimiter and was able to accomplish the expected though I
got some schema validation errors in VS.NET but no issues at run time.
Thanks again,
Kiran Pabba
Pabba wrote:
> Thanks Jan, it works fine with the instance without spaces across
> groups but I have a difference in my actual instance which is:
>
> Instead of empty lines(without spaces) between G1 and G2(i.e all
> groups) I have empty lines with spaces and due to this when I validate
> the schema with my instance I get error similar to:
>
> "Unexpected data found while looking for:
> ' '
> ' '
> ' '
> The current definition being parsed is Childs. The stream offset where
> the error occured is 1872. The line number where the error occured is
> 27. The column where the error occured is 0."
>
> To test you can use the same instance published before and just modify
> line number 26(empty line) with spaces.
>
> Appreciate your help.
>
> Thanks again,
> Kiran
>
> Jan Eliasen wrote:
> > On 4 Jan 2007 12:25:29 -0800, "Pabba" <kiran.pabba@[EMAIL PROTECTED]
> wrote:
> >
> > >I have a flat-file similar to the one listed below and my problem is
to
> > >create a hierarchical Xml structure out of it.
> >
> > >I was able to build a schema (thanks to Jan) which looks like:
> > You're welcome. And I suppose I'd better keep the help coming :-)
> > Sorry I haven't answered your question in the original thread - been
> > busy the last couple of days :-/
> >
> > Try the schema located in
> > http://www.eliasen.dk/biztalk/flatfilespacesidentifier2.zip
- modify
> > it to suit your naming conventions, as I am not sure I have followed
> > them quite thourougly (spelling?).
> >
> > --
> > eliasen, representing himself and not the company he works for.
> >
> > Private blog: http://blog.eliasen.dk
> >
> > Private email: jan@[EMAIL PROTECTED]
|
