yeah I was just wondering -- AFAIK it seems that a closing </event> tag isn´t really required with XML attributes.

However, I *knew* you´d find a way sooner or later (patting on your back :-))

------
batta, bing! Hey .. this XMLexport.class.asp is kind of fun to rewrite
------

You rewrote that ? Wow, I thought you were using the ASP version of Adobe´s query2xml example as starting point

Cheers,
Günter Schenk
Adobe Community Expert, Dreamweaver

AFAIK it seems that a closing </event> tag isn´t really required with XML
attributes.

It is for this because with a recurring event, I have to nest a second tag
called pattern within a particular event. For a recurring event, the final
xml has to look like:

<event title="Test Event 5" description="every second tuesday"
startDate="2007-07-01" endDate="2007-07-31" allDay="1" eventType="weekly">
<pattern sun="0" sat="0" fri="0" thu="0" wed="0" tue="1" mon="0" recur="2"
/>
</event>

whereas all the events that are one time have to be in attributes in order
to work with the ActionScript in the Flash. See? Not nodes and not
attributes. I need a "mixed" alternative.
>
> However, I *knew* you´d find a way sooner or later (patting on your back
> :-))

Thanks!

> You rewrote that ? Wow, I thought you were using the ASP version of
> Adobe´s query2xml example as starting point

I tried to do that .. it only produced nodes and I couldn't figure out how
to get it to produce attributes. It turned out to work better to modify the
XMLExport class in the extension to produce the nested tag and closing node.

Anyway .. just have to get the nested pattern tag with its attributes
feeding in from the database to add to the XML and I'm there.

Thanks for your valuable input! When I get past this, I may write an
article on "Extending the XML Export Extension".

Nancy