Select the XML output option for the button.It will create the xdp structure - but then you will need to use XSLT to format it.See this download example: http://www.emlvoting.org and see under \download and \filesDW

Steve,OK - I'll circle back around on this later this week. I'm assuming its something to do with the setup on my Win XP laptop that it does not like. But I'll see if I can isolate something - and I'll try the delete / repair trick.Thanks, DW

Just try not using the file extension .xml - that usually is enough to step byu the virus checker.Or check the settings for your virus SW to ignore XML....

Probably a good job - since my 7.1 does not work - but my old 7.0 is still working OK!I did realise this bi-install was happening - since the install shield specifically says - "installing to Designer 7.1 directory".DW

I ordered the update from my existing Adobe 7.0.5 last week - I'm beginning to think I may just have wasted $45. I weas hoping this new version would correct problems with XML outputting and designer handling of attributes in elements. Having installed it - and then re-installed it - and then repair...

I ordered the update from my existing Adobe 7.0.5 last week - I'm beginning to think I may just have wasted $45. I weas hoping this new version would correct problems with XML outputting and designer handling of attributes in elements.Having installed it - and then re-installed it - and then repaire...

The only solution here is to use XSLT to clean-up the mess.I was able to finally get my xslt working so that it re-formats the xdp output into normal XML.It should not be this hard to do all this. Ho hum.DW

Ok - I figured this out - in the xdp - there are two sections -<br /><br /><xfa:datasets xmlns:xfa="http://www.xfa.org/schema/xfa-data/1.0/"<br />><xfa:data> <br /><br />and <br /><br />><dd:dataDescription xmlns:dd="http://ns.adobe.com/data-description/" dd:name="xdp"<br />><xdp:xdp xmlns:xdp="htt...

I was correct on this - the DataConnection parser only works for XDP formatted files - not regular XML. Therefore this runtime error goes away - when you change your XML example to have XDP header and footer tags.

Hmmm, having experimented with this - the only way to change the output formatting is using a DataConnection. These are a bit gnarly to setup - you'll need to import an XDP formatted XML instance to use as a reference layout.I did try the xsl - it threw an error message dialogue at me - but gave me ...