RE: Error: "The same table (tableName) cannot be the child table in two nested relations"

Is there any way of working around this issue?

Is this a platform limitation, or a general programming limitation?

 

Cláudio Jorge Vieira Teixeira

IEETA-Instituto de Engenharia Electrónica e Telemática de Aveiro
Universidade de Aveiro
Campus Universitário de Santiago
3810-193 Aveiro

---

From: xmlschema-dev-request@xxxxxx [mailto:xmlschema-dev-request@xxxxxx] On Behalf Of firas
Sent: sábado, 17 de Abril de 2004 7:32
To: xmlschema-dev@xxxxxx
Subject: FW: Error: "The same table (tableName) cannot be the child table in two nested relations"

 

Hello:

 

Since Dfg was repeated under two different elements:

 

1-    squencia

2-    seq2

 

And Dataset Object for .net does not identify same element under two different elements

So just in case dfg have no attributes or child
Elements this can be done….

 

Regards

 

 

 

Firas Darweesh

Rapid Application Developer

Lootah IT Solutions

 

 

To: xmlschema-dev@xxxxxx
Subject: Error: "The same table (tableName) cannot be the child table in two nested relations"

 

Hi, I’m trying to load a schema into a .net program, but I’m getting this error:

“The same table (dfg) cannot be the child table in two nested relations”

 

My schema is as follows:

 

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">

       <xs:element name="teste">

             <xs:annotation>

                    <xs:documentation>Comment describing your root element</xs:documentation>

             </xs:annotation>

             <xs:complexType>

                    <xs:sequence>

                           <xs:element name="sequencia" type="sequenciaType"/>

                           <xs:element name="seq2" type="sequenciaType"/>

                    </xs:sequence>

             </xs:complexType>

       </xs:element>

       <xs:complexType name="sequenciaType">

             <xs:sequence>

                    <xs:element name="teste1"/>

                    <xs:element name="dfg" type="xpto"/>

                    <xs:element name="sdfhgfgh"/>

             </xs:sequence>

       </xs:complexType>

       <xs:complexType name="xpto">

             <xs:sequence>

                    <xs:element name="grrr" type="xs:gYearMonth"/>

                    <xs:element name="lsdkf" type="xs:duration"/>

             </xs:sequence>

       </xs:complexType>

       <xs:complexType name="comSeq">

             <xs:sequence>

                    <xs:element name="seqPP" type="sequenciaType"/>

             </xs:sequence>

       </xs:complexType>

</xs:schema>

 

Basically I have two elements of a complex type that on it’s turn has on element of another complex type. It is this last complex type that causes the error..

Is this normal? What can I do to prevent this kind of situation?

 

Thanks in advance

 

 

 

 

Cláudio Jorge Vieira Teixeira

IEETA-Instituto de Engenharia Electrónica e Telemática de Aveiro
Universidade de Aveiro
Campus Universitário de Santiago
3810-193 Aveiro