Best way to import XML Files

[Fairlight]

>From inside the gravity well of a singularity, George Simon shouted:
> This is basically the same way I did it.
> I just finished writing the code and it seems to work just fine.
> I discovered that filePro will let you use graphic characters as field and
> record delimiters, so I used chr("249") which is a period in the middle of
> the line ( · ) as both my field and record delimiters.

I'm not sure how wise that is.  I'm no expert on XML, but since there's
nothing you can put in a DTD that allows for those extra characters, and
since it's not in a comment, it seems like it -should- result in a parser
saying it's not a well-structured file.

That said, I tried it in both perl with XML::Parser and loading it raw in
IE and neither blew up.  I actually expected XML::Parser to entirely crash
and burn, as expat is notorious for being...curmudgeonish.  It appears to
hve parsed okay.  IE parsed okay but displayed a funny box in the XML
stylesheet it uses (IE 5.5).  

It just doesn't -seem- like a good idea to have those extra non-XML
character out there, uncommented.  I'm not sure every parser will be so
friendly about it.  Whitespace is irrelevant, but that's -not- whitespace.

Would someone with more experience with XML and various parsers care to
comment on the wiseness of the cited methodology?

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html