Weird behaviour with SSIS 2008 and XSD's with maxOccurs attributes

Hi folks,

Has anyone used an XSD that contains maxOccurs attributes in the sequence tags from within an SSIS 2008 XML data source??

For example: <xs:sequenceminOccurs="1"maxOccurs="20">

I am using such an XSD, and for some reason the 'Output name' dropdown in the 'Columns' tab of the XML Source Editor contains the various XSD elements suffixed with 'sequence_1', 'sequence_2', 'sequence_3', and so forth.

For example:

'ExportData__sequence_1'

'ExportData__sequence_1__Quote'

...

'ExportData__sequence_2'

'ExportData__sequence_2__Risk'

...

Removing the maxOccurs from the XSD removes these 'sequence' suffixes from the XML Source Editor. I've no idea of the reasons for this behaviour, but it is preventing the successful loading of XML data because the XML contains no such elements as 'ExportData__sequence_1__Quote' - the superfluous 'sequence_1' causes the legitimate elements of 'ExportData__Quote' for example to be missed.

Can anybody shed any light on why SSIS 2008 would be doing this, and how to work around it WITHOUT modifying the XSD to remove the maxOccurs attributes??

Many thanks!!
Aaron Morgan.