Is there a standard for this? Failing that does anyone have a preferred layout?

If neither I'll probably go for

<Table Name>
<Row>
<Field Name>
data
</Field>
...
...
<Field Name>
data
</Field>
</Row>
...
...
</Table>


Roy Lambert

Roy,

What you have laid out is sensible AFAIK.

Honestly I tend to just use ClientDataset, and Save after setting the save-format to XML.

Then I can just use a CDS to reload the data later & I don't have to worry my little head about the whole process of serializing the data.

I would imagine there could be issues with escape characters which the CDS is probably coded to cope with, but which might trip you up otherwise.

i.e. say you want to save an XML document in your dataset! You'll have to add code to cope with that possibly confusing your parser, if you write one yourself.

Roy,

<< Is there a standard for this? Failing that does anyone have a preferred
layout? >>

You do know that the EDB import/export supports XML, correct ?  It also
escapes any XML in CLOBs for you in the process.

Tim Young
Elevate Software
www.elevatesoft.com

Tim

>You do know that the EDB import/export supports XML, correct ? It also
>escapes any XML in CLOBs for you in the process.

I do as of about 15 seconds ago <vbg>

I'll have a look at what your version does and copy it for my nlhStrTable and query generator which is where I'm thinking of using it

Roy

Roy,

<< I'll have a look at what your version does and copy it for my nlhStrTable
and query generator which is where I'm thinking of using it >>

It's very basic, but I think it should do the job.

Tim Young
Elevate Software
www.elevatesoft.com