Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Nested elements in XML?

5 posts in General Discussion Last posting was on 2005-12-09 18:46:58.0Z
Henry T. Ferguson Posted on 2005-12-08 19:29:35.0Z
From: "Henry T. Ferguson" <henry@coaxis.net>
Newsgroups: ianywhere.public.mbusinessanywhere.general
Subject: Nested elements in XML?
Lines: 69
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: 63.95.90.138
X-Original-NNTP-Posting-Host: 63.95.90.138
Message-ID: <4398899f$1@forums-1-dub>
Date: 8 Dec 2005 11:29:35 -0800
X-Trace: forums-1-dub 1134070175 63.95.90.138 (8 Dec 2005 11:29:35 -0800)
X-Original-Trace: 8 Dec 2005 11:29:35 -0800, 63.95.90.138
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:665
Article PK: 9007

(M-Biz Application Edition 5.5 b164 on Windows)

We are trying to nest elements in our XML and can't figure out how to write
the XSD to map to them. We understand that this isn't a necessary nesting,
our ultimate implementation will be much more sophisticated. We're just
trying to get something to work at all, then get complicated.....

Here are the errors from synch_error.log:

[Thu Dec 08 11:07:14 2005] [error] (3324) Unknown data type for
column(Address) in XSD for db(Customers)
[Thu Dec 08 11:07:14 2005] [error] (3324) mammutparser: Error parsing XSD
for db(Customers)
[Thu Dec 08 11:07:14 2005] [error] (3324) Unable to parse mammut data set
for 'Customers'

Here is a sample of the XML, (below is the XSD):
_________________________________

<?xml version="1.0" encoding="iso-8859-1" ?>
<root>
<Customers>
<CustomerID>1643</CustomerID>
<CustomerName>FAMOUS SAM'S #09</CustomerName>
<Address>
<Street>123 Main</Street>
<City>Portland</City>
</Address>
</Customers>
<Customers>
<CustomerID>1654</CustomerID>
<CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
<Address>
<Street>8651 SW 7th Avenue</Street>
<City>Seattle</City>
</Address>
</Customers>
</root>
_________________________________

Here's our attempt at the XSD:

_________________________________

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:dt="urn:schemas-microsoft-com:datatypes"
xmlns:msch="urn:schemas-microsoft-com:mapping-schema">
<xsd:element name="Customers" msch:relation="Customers"
type="Customers_type"/>
<xsd:complexType name="Customers_type">
<xsd:element name="CustomerID" type="xsd:string"/>
<xsd:element name="CustomerName" type="xsd:string"/>
<xsd:element name="Address" type="Address_type"/>
<xsd:key name="PrimaryKey">
<xsd:selector xpath="."/>
<xsd:field xpath="@CustomerID"/>
</xsd:key>
</xsd:complexType>

<xsd:complexType name="Address_type">
<xsd:element name="Street" type="xsd:string"/>
<xsd:element name="City" type="xsd:string"/>
</xsd:complexType>

</xsd:schema>
_________________________________


Enrico Pallazzo Posted on 2005-12-08 20:25:48.0Z
From: "Enrico Pallazzo" <enricopallazzo@myway.com>
Newsgroups: ianywhere.public.mbusinessanywhere.general
References: <4398899f$1@forums-1-dub>
Subject: Re: Nested elements in XML?
Lines: 122
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-RFC2646: Format=Flowed; Response
X-Original-NNTP-Posting-Host: vpn-dub-179.sybase.com
Message-ID: <439894c2$1@forums-2-dub>
X-Original-Trace: 8 Dec 2005 12:17:06 -0800, vpn-dub-179.sybase.com
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 8 Dec 2005 12:17:07 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 8 Dec 2005 12:25:48 -0800
X-Trace: forums-1-dub 1134073548 10.22.108.75 (8 Dec 2005 12:25:48 -0800)
X-Original-Trace: 8 Dec 2005 12:25:48 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:666
Article PK: 17754

no nesting in the XML, if you want to do your example you need to either
just flatten out the data:

<root>
<Customers>
<CustomerID>1643</CustomerID>
<CustomerName>FAMOUS SAM'S #09</CustomerName>
<Street>123 Main</Street>
<City>Portland</City>
</Customers>
<Customers>
<CustomerID>1654</CustomerID>
<CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
<Street>8651 SW 7th Avenue</Street>
<City>Seattle</City>
</Customers>
</root>


or I think it would be good to have two databases: customer and address

<?xml version="1.0" encoding="iso-8859-1" ?>
<root>
<Customers>
<CustomerID>1643</CustomerID>
<CustomerName>FAMOUS SAM'S #09</CustomerName>
<AddressID>1</AddressID>
</Customers>
<Customers>
<CustomerID>1654</CustomerID>
<CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
<AddressID>2</AddressID>
</Customers>
</root>

<?xml version="1.0" encoding="iso-8859-1" ?>
<root>
<Address>
<id>1</id>
<Street>123 Main</Street>
<City>Portland</City>
</Address>
<Address>
<id>2</id>
<Street>8651 SW 7th Avenue</Street>
<City>Seattle</City>
</Address>
</root>

"Henry T. Ferguson" <henry@coaxis.net> wrote in message
news:4398899f$1@forums-1-dub...
> (M-Biz Application Edition 5.5 b164 on Windows)
>
> We are trying to nest elements in our XML and can't figure out how to
> write the XSD to map to them. We understand that this isn't a necessary
> nesting, our ultimate implementation will be much more sophisticated.
> We're just trying to get something to work at all, then get
> complicated.....
>
> Here are the errors from synch_error.log:
>
> [Thu Dec 08 11:07:14 2005] [error] (3324) Unknown data type for
> column(Address) in XSD for db(Customers)
> [Thu Dec 08 11:07:14 2005] [error] (3324) mammutparser: Error parsing XSD
> for db(Customers)
> [Thu Dec 08 11:07:14 2005] [error] (3324) Unable to parse mammut data set
> for 'Customers'
>
> Here is a sample of the XML, (below is the XSD):
> _________________________________
>
> <?xml version="1.0" encoding="iso-8859-1" ?>
> <root>
> <Customers>
> <CustomerID>1643</CustomerID>
> <CustomerName>FAMOUS SAM'S #09</CustomerName>
> <Address>
> <Street>123 Main</Street>
> <City>Portland</City>
> </Address>
> </Customers>
> <Customers>
> <CustomerID>1654</CustomerID>
> <CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
> <Address>
> <Street>8651 SW 7th Avenue</Street>
> <City>Seattle</City>
> </Address>
> </Customers>
> </root>
> _________________________________
>
> Here's our attempt at the XSD:
>
> _________________________________
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:dt="urn:schemas-microsoft-com:datatypes"
> xmlns:msch="urn:schemas-microsoft-com:mapping-schema">
> <xsd:element name="Customers" msch:relation="Customers"
> type="Customers_type"/>
> <xsd:complexType name="Customers_type">
> <xsd:element name="CustomerID" type="xsd:string"/>
> <xsd:element name="CustomerName" type="xsd:string"/>
> <xsd:element name="Address" type="Address_type"/>
> <xsd:key name="PrimaryKey">
> <xsd:selector xpath="."/>
> <xsd:field xpath="@CustomerID"/>
> </xsd:key>
> </xsd:complexType>
>
> <xsd:complexType name="Address_type">
> <xsd:element name="Street" type="xsd:string"/>
> <xsd:element name="City" type="xsd:string"/>
> </xsd:complexType>
>
> </xsd:schema>
> _________________________________
>


Henry T. Ferguson Posted on 2005-12-08 21:32:10.0Z
From: "Henry T. Ferguson" <henry@coaxis.net>
Newsgroups: ianywhere.public.mbusinessanywhere.general
References: <4398899f$1@forums-1-dub> <439894c2$1@forums-2-dub>
Subject: Re: Nested elements in XML?
Lines: 134
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 63.95.90.138
X-Original-NNTP-Posting-Host: 63.95.90.138
Message-ID: <4398a65a$1@forums-1-dub>
Date: 8 Dec 2005 13:32:10 -0800
X-Trace: forums-1-dub 1134077530 63.95.90.138 (8 Dec 2005 13:32:10 -0800)
X-Original-Trace: 8 Dec 2005 13:32:10 -0800, 63.95.90.138
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:667
Article PK: 9010

Wow, that's a bummer. Does this mean that we would have to use Ultralight
to do more sophisticated relations? No M-Business apps built with the XML
API can see deeper than one level of XML?
Let me know,

Thanks.

Henry

"Enrico Pallazzo" <enricopallazzo@myway.com> wrote in message
news:439894c2$1@forums-2-dub...
> no nesting in the XML, if you want to do your example you need to either
> just flatten out the data:
>
> <root>
> <Customers>
> <CustomerID>1643</CustomerID>
> <CustomerName>FAMOUS SAM'S #09</CustomerName>
> <Street>123 Main</Street>
> <City>Portland</City>
> </Customers>
> <Customers>
> <CustomerID>1654</CustomerID>
> <CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
> <Street>8651 SW 7th Avenue</Street>
> <City>Seattle</City>
> </Customers>
> </root>
>
>
> or I think it would be good to have two databases: customer and address
>
> <?xml version="1.0" encoding="iso-8859-1" ?>
> <root>
> <Customers>
> <CustomerID>1643</CustomerID>
> <CustomerName>FAMOUS SAM'S #09</CustomerName>
> <AddressID>1</AddressID>
> </Customers>
> <Customers>
> <CustomerID>1654</CustomerID>
> <CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
> <AddressID>2</AddressID>
> </Customers>
> </root>
>
> <?xml version="1.0" encoding="iso-8859-1" ?>
> <root>
> <Address>
> <id>1</id>
> <Street>123 Main</Street>
> <City>Portland</City>
> </Address>
> <Address>
> <id>2</id>
> <Street>8651 SW 7th Avenue</Street>
> <City>Seattle</City>
> </Address>
> </root>
>
> "Henry T. Ferguson" <henry@coaxis.net> wrote in message
> news:4398899f$1@forums-1-dub...
>> (M-Biz Application Edition 5.5 b164 on Windows)
>>
>> We are trying to nest elements in our XML and can't figure out how to
>> write the XSD to map to them. We understand that this isn't a necessary
>> nesting, our ultimate implementation will be much more sophisticated.
>> We're just trying to get something to work at all, then get
>> complicated.....
>>
>> Here are the errors from synch_error.log:
>>
>> [Thu Dec 08 11:07:14 2005] [error] (3324) Unknown data type for
>> column(Address) in XSD for db(Customers)
>> [Thu Dec 08 11:07:14 2005] [error] (3324) mammutparser: Error parsing XSD
>> for db(Customers)
>> [Thu Dec 08 11:07:14 2005] [error] (3324) Unable to parse mammut data set
>> for 'Customers'
>>
>> Here is a sample of the XML, (below is the XSD):
>> _________________________________
>>
>> <?xml version="1.0" encoding="iso-8859-1" ?>
>> <root>
>> <Customers>
>> <CustomerID>1643</CustomerID>
>> <CustomerName>FAMOUS SAM'S #09</CustomerName>
>> <Address>
>> <Street>123 Main</Street>
>> <City>Portland</City>
>> </Address>
>> </Customers>
>> <Customers>
>> <CustomerID>1654</CustomerID>
>> <CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
>> <Address>
>> <Street>8651 SW 7th Avenue</Street>
>> <City>Seattle</City>
>> </Address>
>> </Customers>
>> </root>
>> _________________________________
>>
>> Here's our attempt at the XSD:
>>
>> _________________________________
>>
>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:dt="urn:schemas-microsoft-com:datatypes"
>> xmlns:msch="urn:schemas-microsoft-com:mapping-schema">
>> <xsd:element name="Customers" msch:relation="Customers"
>> type="Customers_type"/>
>> <xsd:complexType name="Customers_type">
>> <xsd:element name="CustomerID" type="xsd:string"/>
>> <xsd:element name="CustomerName" type="xsd:string"/>
>> <xsd:element name="Address" type="Address_type"/>
>> <xsd:key name="PrimaryKey">
>> <xsd:selector xpath="."/>
>> <xsd:field xpath="@CustomerID"/>
>> </xsd:key>
>> </xsd:complexType>
>>
>> <xsd:complexType name="Address_type">
>> <xsd:element name="Street" type="xsd:string"/>
>> <xsd:element name="City" type="xsd:string"/>
>> </xsd:complexType>
>>
>> </xsd:schema>
>> _________________________________
>>
>
>


Enrico Pallazzo Posted on 2005-12-09 15:20:53.0Z
From: "Enrico Pallazzo" <enricopallazzo@myway.com>
Newsgroups: ianywhere.public.mbusinessanywhere.general
References: <4398899f$1@forums-1-dub> <439894c2$1@forums-2-dub> <4398a65a$1@forums-1-dub>
Subject: Re: Nested elements in XML?
Lines: 150
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-RFC2646: Format=Flowed; Response
X-Original-NNTP-Posting-Host: vpn-dub-024.sybase.com
Message-ID: <43999ec2@forums-2-dub>
X-Original-Trace: 9 Dec 2005 07:12:02 -0800, vpn-dub-024.sybase.com
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 9 Dec 2005 07:12:05 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 9 Dec 2005 07:20:53 -0800
X-Trace: forums-1-dub 1134141653 10.22.108.75 (9 Dec 2005 07:20:53 -0800)
X-Original-Trace: 9 Dec 2005 07:20:53 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:668
Article PK: 9008


"Henry T. Ferguson" <henry@coaxis.net> wrote in message
news:4398a65a$1@forums-1-dub...
> Wow, that's a bummer. Does this mean that we would have to use Ultralight
> to do more sophisticated relations?

Ultralight is database, the db_pod is a datastore. So yes if you want to do
a join of an address and a customer through a foriegn key, you can do that
with SQL in Ultralight or manually with the db_pod.

> No M-Business apps built with the XML API can see deeper than one level of
> XML?
> Let me know,
>

Its not that we can't parse the XML, its that we have to map the XML to the
format of the db pod. It is a simple record based format where each record
can contain a seriers of columns.

> Thanks.
>
> Henry
> "Enrico Pallazzo" <enricopallazzo@myway.com> wrote in message
> news:439894c2$1@forums-2-dub...
>> no nesting in the XML, if you want to do your example you need to either
>> just flatten out the data:
>>
>> <root>
>> <Customers>
>> <CustomerID>1643</CustomerID>
>> <CustomerName>FAMOUS SAM'S #09</CustomerName>
>> <Street>123 Main</Street>
>> <City>Portland</City>
>> </Customers>
>> <Customers>
>> <CustomerID>1654</CustomerID>
>> <CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
>> <Street>8651 SW 7th Avenue</Street>
>> <City>Seattle</City>
>> </Customers>
>> </root>
>>
>>
>> or I think it would be good to have two databases: customer and address
>>
>> <?xml version="1.0" encoding="iso-8859-1" ?>
>> <root>
>> <Customers>
>> <CustomerID>1643</CustomerID>
>> <CustomerName>FAMOUS SAM'S #09</CustomerName>
>> <AddressID>1</AddressID>
>> </Customers>
>> <Customers>
>> <CustomerID>1654</CustomerID>
>> <CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
>> <AddressID>2</AddressID>
>> </Customers>
>> </root>
>>
>> <?xml version="1.0" encoding="iso-8859-1" ?>
>> <root>
>> <Address>
>> <id>1</id>
>> <Street>123 Main</Street>
>> <City>Portland</City>
>> </Address>
>> <Address>
>> <id>2</id>
>> <Street>8651 SW 7th Avenue</Street>
>> <City>Seattle</City>
>> </Address>
>> </root>
>>
>> "Henry T. Ferguson" <henry@coaxis.net> wrote in message
>> news:4398899f$1@forums-1-dub...
>>> (M-Biz Application Edition 5.5 b164 on Windows)
>>>
>>> We are trying to nest elements in our XML and can't figure out how to
>>> write the XSD to map to them. We understand that this isn't a necessary
>>> nesting, our ultimate implementation will be much more sophisticated.
>>> We're just trying to get something to work at all, then get
>>> complicated.....
>>>
>>> Here are the errors from synch_error.log:
>>>
>>> [Thu Dec 08 11:07:14 2005] [error] (3324) Unknown data type for
>>> column(Address) in XSD for db(Customers)
>>> [Thu Dec 08 11:07:14 2005] [error] (3324) mammutparser: Error parsing
>>> XSD for db(Customers)
>>> [Thu Dec 08 11:07:14 2005] [error] (3324) Unable to parse mammut data
>>> set for 'Customers'
>>>
>>> Here is a sample of the XML, (below is the XSD):
>>> _________________________________
>>>
>>> <?xml version="1.0" encoding="iso-8859-1" ?>
>>> <root>
>>> <Customers>
>>> <CustomerID>1643</CustomerID>
>>> <CustomerName>FAMOUS SAM'S #09</CustomerName>
>>> <Address>
>>> <Street>123 Main</Street>
>>> <City>Portland</City>
>>> </Address>
>>> </Customers>
>>> <Customers>
>>> <CustomerID>1654</CustomerID>
>>> <CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
>>> <Address>
>>> <Street>8651 SW 7th Avenue</Street>
>>> <City>Seattle</City>
>>> </Address>
>>> </Customers>
>>> </root>
>>> _________________________________
>>>
>>> Here's our attempt at the XSD:
>>>
>>> _________________________________
>>>
>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>> xmlns:dt="urn:schemas-microsoft-com:datatypes"
>>> xmlns:msch="urn:schemas-microsoft-com:mapping-schema">
>>> <xsd:element name="Customers" msch:relation="Customers"
>>> type="Customers_type"/>
>>> <xsd:complexType name="Customers_type">
>>> <xsd:element name="CustomerID" type="xsd:string"/>
>>> <xsd:element name="CustomerName" type="xsd:string"/>
>>> <xsd:element name="Address" type="Address_type"/>
>>> <xsd:key name="PrimaryKey">
>>> <xsd:selector xpath="."/>
>>> <xsd:field xpath="@CustomerID"/>
>>> </xsd:key>
>>> </xsd:complexType>
>>>
>>> <xsd:complexType name="Address_type">
>>> <xsd:element name="Street" type="xsd:string"/>
>>> <xsd:element name="City" type="xsd:string"/>
>>> </xsd:complexType>
>>>
>>> </xsd:schema>
>>> _________________________________
>>>
>>
>>
>
>


Henry T. Ferguson Posted on 2005-12-09 18:46:58.0Z
From: "Henry T. Ferguson" <henry@coaxis.net>
Newsgroups: ianywhere.public.mbusinessanywhere.general
References: <4398899f$1@forums-1-dub> <439894c2$1@forums-2-dub> <4398a65a$1@forums-1-dub> <43999ec2@forums-2-dub>
Subject: Re: Nested elements in XML?
Lines: 159
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 63.95.90.138
X-Original-NNTP-Posting-Host: 63.95.90.138
Message-ID: <4399d122@forums-1-dub>
Date: 9 Dec 2005 10:46:58 -0800
X-Trace: forums-1-dub 1134154018 63.95.90.138 (9 Dec 2005 10:46:58 -0800)
X-Original-Trace: 9 Dec 2005 10:46:58 -0800, 63.95.90.138
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:669
Article PK: 17755

Thanks Enrico - we'll continue with XML and see where we end-up,

Henry

"Enrico Pallazzo" <enricopallazzo@myway.com> wrote in message
news:43999ec2@forums-2-dub...
>
> "Henry T. Ferguson" <henry@coaxis.net> wrote in message
> news:4398a65a$1@forums-1-dub...
>> Wow, that's a bummer. Does this mean that we would have to use
>> Ultralight to do more sophisticated relations?
>
> Ultralight is database, the db_pod is a datastore. So yes if you want to
> do a join of an address and a customer through a foriegn key, you can do
> that with SQL in Ultralight or manually with the db_pod.
>
>> No M-Business apps built with the XML API can see deeper than one level
>> of XML?
>> Let me know,
>>
>
> Its not that we can't parse the XML, its that we have to map the XML to
> the format of the db pod. It is a simple record based format where each
> record can contain a seriers of columns.
>
>> Thanks.
>>
>> Henry
>> "Enrico Pallazzo" <enricopallazzo@myway.com> wrote in message
>> news:439894c2$1@forums-2-dub...
>>> no nesting in the XML, if you want to do your example you need to either
>>> just flatten out the data:
>>>
>>> <root>
>>> <Customers>
>>> <CustomerID>1643</CustomerID>
>>> <CustomerName>FAMOUS SAM'S #09</CustomerName>
>>> <Street>123 Main</Street>
>>> <City>Portland</City>
>>> </Customers>
>>> <Customers>
>>> <CustomerID>1654</CustomerID>
>>> <CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
>>> <Street>8651 SW 7th Avenue</Street>
>>> <City>Seattle</City>
>>> </Customers>
>>> </root>
>>>
>>>
>>> or I think it would be good to have two databases: customer and address
>>>
>>> <?xml version="1.0" encoding="iso-8859-1" ?>
>>> <root>
>>> <Customers>
>>> <CustomerID>1643</CustomerID>
>>> <CustomerName>FAMOUS SAM'S #09</CustomerName>
>>> <AddressID>1</AddressID>
>>> </Customers>
>>> <Customers>
>>> <CustomerID>1654</CustomerID>
>>> <CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
>>> <AddressID>2</AddressID>
>>> </Customers>
>>> </root>
>>>
>>> <?xml version="1.0" encoding="iso-8859-1" ?>
>>> <root>
>>> <Address>
>>> <id>1</id>
>>> <Street>123 Main</Street>
>>> <City>Portland</City>
>>> </Address>
>>> <Address>
>>> <id>2</id>
>>> <Street>8651 SW 7th Avenue</Street>
>>> <City>Seattle</City>
>>> </Address>
>>> </root>
>>>
>>> "Henry T. Ferguson" <henry@coaxis.net> wrote in message
>>> news:4398899f$1@forums-1-dub...
>>>> (M-Biz Application Edition 5.5 b164 on Windows)
>>>>
>>>> We are trying to nest elements in our XML and can't figure out how to
>>>> write the XSD to map to them. We understand that this isn't a necessary
>>>> nesting, our ultimate implementation will be much more sophisticated.
>>>> We're just trying to get something to work at all, then get
>>>> complicated.....
>>>>
>>>> Here are the errors from synch_error.log:
>>>>
>>>> [Thu Dec 08 11:07:14 2005] [error] (3324) Unknown data type for
>>>> column(Address) in XSD for db(Customers)
>>>> [Thu Dec 08 11:07:14 2005] [error] (3324) mammutparser: Error parsing
>>>> XSD for db(Customers)
>>>> [Thu Dec 08 11:07:14 2005] [error] (3324) Unable to parse mammut data
>>>> set for 'Customers'
>>>>
>>>> Here is a sample of the XML, (below is the XSD):
>>>> _________________________________
>>>>
>>>> <?xml version="1.0" encoding="iso-8859-1" ?>
>>>> <root>
>>>> <Customers>
>>>> <CustomerID>1643</CustomerID>
>>>> <CustomerName>FAMOUS SAM'S #09</CustomerName>
>>>> <Address>
>>>> <Street>123 Main</Street>
>>>> <City>Portland</City>
>>>> </Address>
>>>> </Customers>
>>>> <Customers>
>>>> <CustomerID>1654</CustomerID>
>>>> <CustomerName>FUMBLES BAR &#38; GRILL</CustomerName>
>>>> <Address>
>>>> <Street>8651 SW 7th Avenue</Street>
>>>> <City>Seattle</City>
>>>> </Address>
>>>> </Customers>
>>>> </root>
>>>> _________________________________
>>>>
>>>> Here's our attempt at the XSD:
>>>>
>>>> _________________________________
>>>>
>>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>>> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>>> xmlns:dt="urn:schemas-microsoft-com:datatypes"
>>>> xmlns:msch="urn:schemas-microsoft-com:mapping-schema">
>>>> <xsd:element name="Customers" msch:relation="Customers"
>>>> type="Customers_type"/>
>>>> <xsd:complexType name="Customers_type">
>>>> <xsd:element name="CustomerID" type="xsd:string"/>
>>>> <xsd:element name="CustomerName" type="xsd:string"/>
>>>> <xsd:element name="Address" type="Address_type"/>
>>>> <xsd:key name="PrimaryKey">
>>>> <xsd:selector xpath="."/>
>>>> <xsd:field xpath="@CustomerID"/>
>>>> </xsd:key>
>>>> </xsd:complexType>
>>>>
>>>> <xsd:complexType name="Address_type">
>>>> <xsd:element name="Street" type="xsd:string"/>
>>>> <xsd:element name="City" type="xsd:string"/>
>>>> </xsd:complexType>
>>>>
>>>> </xsd:schema>
>>>> _________________________________
>>>>
>>>
>>>
>>
>>
>
>