General

Re: Yet another "cant open in Design Mode"

franck — Tue, 15 Nov 2005 03:34:03 GMT

OK, we are making progress here. Are you using the "Repeating Recursive Section" control? Can you tried to use regular "Repeating Section" (with another repeating section inside)?

Franck

Re: Yet another "cant open in Design Mode"

adamw — Tue, 15 Nov 2005 02:49:49 GMT

Have tried that. It doesn't seem to crash when you Open it anymore, but it still will not create the recursive repeating group. It just seems to ignore the my:list altogether and doesnt even create a choice section for it.

Re: Yet another "cant open in Design Mode"

franck — Tue, 15 Nov 2005 01:59:29 GMT

Hi Adam,

If you try a few of the features that you are trying to implement in a new blank form, with a schema totally re-designed from scratch, does it work?

Regards,

Franck Dauché

Re: Yet another "cant open in Design Mode"

adamw — Tue, 15 Nov 2005 00:33:13 GMT

I am not having any luck at all debugging this way.

I also can not get Infopath to produce the recursive repeating section (my:list) when I drag "sections" to InfoPath. There must be something Infopath fundamentally doesn't like about the schema.

Re: Yet another "cant open in Design Mode"

franck — Mon, 14 Nov 2005 06:09:51 GMT

Hi Adam,

Did you try to delete the above part from your schema and re-create it from scratch? You can add items one at a time to see if one makes your form choke.

Regards,

Franck Dauché

Yet another "cant open in Design Mode"

adamw — Mon, 14 Nov 2005 04:12:06 GMT

Hi

Running Infopath SP1/Windows XP.

I am no longer able to open my form in Design view as I get the error "Infopath has encountered an error. The operation failed".

Now, when I rip out part of the XSL on one of my views it works again, but as soon as I drag part of my data source tree onto the form to create the controls, the error reoccurs (after I save and reload). Now, I understand that the XSL generated is going to be dependent on the schema (myschema.xsd) so I have been fiddling with the schema with some success. I can get it working, but then it no longer does what I want. This is the part of the schema it is having trouble generating working XSL from (note the recursion):

<xsd:element name="sections">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="my:section" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="section">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="my:list" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute ref="heading"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="list">
<xsd:complexType>
<xsd:sequence>
<xsd:choice>
<xsd:element ref="my:condition" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="my:list-item" minOccurs="0" maxOccurs="unbounded"/>
</xsd:choice>
</xsd:sequence>
<xsd:attribute ref="type"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="condition">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="my:list-item-part" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute ref="specialexpiry"/>
<xsd:attribute ref="indextext"/>
<xsd:attribute ref="number"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="list-item-part">
<xsd:complexType>
<xsd:choice>
<xsd:element ref="my:content" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="my:list" minOccurs="0" maxOccurs="unbounded"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:element name="content" type="xsd:string"/>
<xsd:element name="list-item">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="my:list-item-part" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute ref="indextext"/>
<xsd:attribute ref="number"/>
</xsd:complexType>
</xsd:element>

Any ideas? In plain English, I have a sections group which contains sections, each section can contain lists, each list can contain either a sequence of list items or a sequence of conditions. Each list item or condition can contain some some text content, or another list.

Any ideas why this would fail?

Regards
Adam