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.

Data Format Exception

7 posts in XML Last posting was on 2009-02-27 21:50:20.0Z
Kevin Arnold Posted on 2009-02-25 16:14:33.0Z
Sender: 3e6f.49a569e0.1804289383@sybase.com
From: Kevin Arnold
Newsgroups: sybase.public.powerbuilder.xml
Subject: Data Format Exception
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <49a56e69.3f0c.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 25 Feb 2009 08:14:33 -0800
X-Trace: forums-1-dub 1235578473 10.22.241.41 (25 Feb 2009 08:14:33 -0800)
X-Original-Trace: 25 Feb 2009 08:14:33 -0800, 10.22.241.41
Lines: 8
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.xml:1803
Article PK: 814348

We recently upgraded from PB 9 to PB 11.5 and when importing
an XML file into our app, we get an error calling
GetParseErrors. The error states the "degree symbol" is
illegal. This same XML file worked fine in PB 9, but now
does not. Anyone know what I can do to fix this?

Thanks,
Kevin


Dave Hauze Posted on 2009-02-26 20:09:22.0Z
From: "Dave Hauze" <david.hauze@steeldynamics.com>
Newsgroups: sybase.public.powerbuilder.xml
References: <49a56e69.3f0c.1681692777@sybase.com>
Subject: Re: Data Format Exception
Lines: 32
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <49a6f6f2$1@forums-1-dub>
Date: 26 Feb 2009 12:09:22 -0800
X-Trace: forums-1-dub 1235678962 10.22.241.152 (26 Feb 2009 12:09:22 -0800)
X-Original-Trace: 26 Feb 2009 12:09:22 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.xml:1807
Article PK: 767941

This may have to do with the switch from ASCII to Unicode. There are some
enumerations for string and blob functions that you can use to properly
format the .XML string (in addition, in the .XML header, what format is
specified, example below).

You might see:
<?xml version="1.0" encoding="ASCII" standalone="yes"?>

Or for Unicode
<?xml version="1.0" encoding="UTF-16LE" standalone="yes"?>
or
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

Depending on which one is being used you may need to use the enumerations
"EncodingANSI!" or "EncodingUTF16LE!" or "EncodingUTF8!"

Hope this helps!

--
Dave Hauze

<Kevin Arnold> wrote in message news:49a56e69.3f0c.1681692777@sybase.com...
> We recently upgraded from PB 9 to PB 11.5 and when importing
> an XML file into our app, we get an error calling
> GetParseErrors. The error states the "degree symbol" is
> illegal. This same XML file worked fine in PB 9, but now
> does not. Anyone know what I can do to fix this?
>
> Thanks,
> Kevin


Kevin Arnold Posted on 2009-02-26 21:54:42.0Z
Sender: 4665.49a5aa7c.1804289383@sybase.com
From: Kevin Arnold
Newsgroups: sybase.public.powerbuilder.xml
Subject: Re: Data Format Exception
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <49a70fa2.6e2b.1681692777@sybase.com>
References: <49a6f6f2$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 26 Feb 2009 13:54:42 -0800
X-Trace: forums-1-dub 1235685282 10.22.241.41 (26 Feb 2009 13:54:42 -0800)
X-Original-Trace: 26 Feb 2009 13:54:42 -0800, 10.22.241.41
Lines: 41
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.xml:1808
Article PK: 814345

I am not doing a string manipulation, I am reading the XML
into the PBDOM_Builder and then get the GetParseErrors.

lpbdom_bldr = Create PBDOM_Builder
lpbdom_doc = lpbdom_bldr.BuildFromFile(is_xml_file_location)
lb_bad_parse = lpbdom_bldr.GetParseErrors(ls_parse_errors)

> This may have to do with the switch from ASCII to Unicode.
> There are some enumerations for string and blob functions
> that you can use to properly format the .XML string (in
> addition, in the .XML header, what format is specified,
> example below).
>
> You might see:
> <?xml version="1.0" encoding="ASCII" standalone="yes"?>
>
> Or for Unicode
> <?xml version="1.0" encoding="UTF-16LE" standalone="yes"?>
> or
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>
> Depending on which one is being used you may need to use
> the enumerations "EncodingANSI!" or "EncodingUTF16LE!" or
> "EncodingUTF8!"
>
> Hope this helps!
>
> --
> Dave Hauze
>
> <Kevin Arnold> wrote in message
> > news:49a56e69.3f0c.1681692777@sybase.com... We recently
> > upgraded from PB 9 to PB 11.5 and when importing an XML
> > file into our app, we get an error calling
> > GetParseErrors. The error states the "degree symbol" is
> > illegal. This same XML file worked fine in PB 9, but now
> does not. Anyone know what I can do to fix this? >
> > Thanks,
> > Kevin
>
>


Dave Hauze Posted on 2009-02-27 13:54:35.0Z
From: "Dave Hauze" <david.hauze@steeldynamics.com>
Newsgroups: sybase.public.powerbuilder.xml
References: <49a6f6f2$1@forums-1-dub> <49a70fa2.6e2b.1681692777@sybase.com>
Subject: Re: Data Format Exception
Lines: 57
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <49a7f09b$1@forums-1-dub>
Date: 27 Feb 2009 05:54:35 -0800
X-Trace: forums-1-dub 1235742875 10.22.241.152 (27 Feb 2009 05:54:35 -0800)
X-Original-Trace: 27 Feb 2009 05:54:35 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.xml:1811
Article PK: 767943

Aaah, did not realize you were using PBDOM... Well, PBDOM_Builder always
uses UTF-16LE Encoding. One thing you need to make sure of is that the
document, if declared as UTF-16LE is actually saved in that format (and not
as simple ASCII Text), a tool like TextPad will help you determine the
actual encoding of the document, and allow you to encode it differently if
necessary. Beyond making sure that the encoding is correct, since that's the
major change from PB 9 and PB 10 and above is the ASCII / Unicode barrier,
I'm not sure where to go from there, maybe someone else will be able to pick
this up and be helpful.

--
Dave Hauze

<Kevin Arnold> wrote in message news:49a70fa2.6e2b.1681692777@sybase.com...
>I am not doing a string manipulation, I am reading the XML
> into the PBDOM_Builder and then get the GetParseErrors.
>
> lpbdom_bldr = Create PBDOM_Builder
> lpbdom_doc = lpbdom_bldr.BuildFromFile(is_xml_file_location)
> lb_bad_parse = lpbdom_bldr.GetParseErrors(ls_parse_errors)
>
>> This may have to do with the switch from ASCII to Unicode.
>> There are some enumerations for string and blob functions
>> that you can use to properly format the .XML string (in
>> addition, in the .XML header, what format is specified,
>> example below).
>>
>> You might see:
>> <?xml version="1.0" encoding="ASCII" standalone="yes"?>
>>
>> Or for Unicode
>> <?xml version="1.0" encoding="UTF-16LE" standalone="yes"?>
>> or
>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>>
>> Depending on which one is being used you may need to use
>> the enumerations "EncodingANSI!" or "EncodingUTF16LE!" or
>> "EncodingUTF8!"
>>
>> Hope this helps!
>>
>> --
>> Dave Hauze
>>
>> <Kevin Arnold> wrote in message
>> > news:49a56e69.3f0c.1681692777@sybase.com... We recently
>> > upgraded from PB 9 to PB 11.5 and when importing an XML
>> > file into our app, we get an error calling
>> > GetParseErrors. The error states the "degree symbol" is
>> > illegal. This same XML file worked fine in PB 9, but now
>> does not. Anyone know what I can do to fix this? >
>> > Thanks,
>> > Kevin
>>
>>


Kevin Arnold Posted on 2009-02-27 19:19:33.0Z
Sender: c73.49a83c54.1804289383@sybase.com
From: Kevin Arnold
Newsgroups: sybase.public.powerbuilder.xml
Subject: Re: Data Format Exception
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <49a83cc5.c87.1681692777@sybase.com>
References: <49a7f09b$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 27 Feb 2009 11:19:33 -0800
X-Trace: forums-1-dub 1235762373 10.22.241.41 (27 Feb 2009 11:19:33 -0800)
X-Original-Trace: 27 Feb 2009 11:19:33 -0800, 10.22.241.41
Lines: 65
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.xml:1812
Article PK: 814347

You nailed it Dave. I had changed the encoding to equal
UTF-16LE in the XML file but did not do a save as Unicode.
When I did the Save As Unicode, the file imported correctly.
Thanks for your help.

> Aaah, did not realize you were using PBDOM... Well,
> PBDOM_Builder always uses UTF-16LE Encoding. One thing
> you need to make sure of is that the document, if
> declared as UTF-16LE is actually saved in that format (and
> not as simple ASCII Text), a tool like TextPad will help
> you determine the actual encoding of the document, and
> allow you to encode it differently if necessary. Beyond
> making sure that the encoding is correct, since that's the
> major change from PB 9 and PB 10 and above is the ASCII /
> Unicode barrier, I'm not sure where to go from there,
> maybe someone else will be able to pick this up and be
> helpful.
>
> --
> Dave Hauze
>
> <Kevin Arnold> wrote in message
> news:49a70fa2.6e2b.1681692777@sybase.com... >I am not
> > doing a string manipulation, I am reading the XML into
> the PBDOM_Builder and then get the GetParseErrors. >
> > lpbdom_bldr = Create PBDOM_Builder
> > lpbdom_doc =
> > lpbdom_bldr.BuildFromFile(is_xml_file_location)
> lb_bad_parse = lpbdom_bldr.GetParseErrors(ls_parse_errors)
> > >> This may have to do with the switch from ASCII to
> Unicode. >> There are some enumerations for string and
> blob functions >> that you can use to properly format the
> XML string (in >> addition, in the .XML header, what
> format is specified, >> example below).
> >>
> >> You might see:
> >> <?xml version="1.0" encoding="ASCII" standalone="yes"?>
> >>
> >> Or for Unicode
> >> <?xml version="1.0" encoding="UTF-16LE"
> standalone="yes"?> >> or
> >> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> >>
> >> Depending on which one is being used you may need to
> use >> the enumerations "EncodingANSI!" or
> "EncodingUTF16LE!" or >> "EncodingUTF8!"
> >>
> >> Hope this helps!
> >>
> >> --
> >> Dave Hauze
> >>
> >> <Kevin Arnold> wrote in message
> >> > news:49a56e69.3f0c.1681692777@sybase.com... We
> recently >> > upgraded from PB 9 to PB 11.5 and when
> importing an XML >> > file into our app, we get an error
> calling >> > GetParseErrors. The error states the "degree
> symbol" is >> > illegal. This same XML file worked fine in
> PB 9, but now >> does not. Anyone know what I can do to
> fix this? > >> > Thanks,
> >> > Kevin
> >>
> >>
>
>


Dave Hauze Posted on 2009-02-27 21:50:20.0Z
From: "Dave Hauze" <david.hauze@steeldynamics.com>
Newsgroups: sybase.public.powerbuilder.xml
References: <49a7f09b$1@forums-1-dub> <49a83cc5.c87.1681692777@sybase.com>
Subject: Re: Data Format Exception
Lines: 73
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <49a8601c@forums-1-dub>
Date: 27 Feb 2009 13:50:20 -0800
X-Trace: forums-1-dub 1235771420 10.22.241.152 (27 Feb 2009 13:50:20 -0800)
X-Original-Trace: 27 Feb 2009 13:50:20 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.xml:1813
Article PK: 814350

Glad I could be of help...

--
Dave Hauze

<Kevin Arnold> wrote in message news:49a83cc5.c87.1681692777@sybase.com...
> You nailed it Dave. I had changed the encoding to equal
> UTF-16LE in the XML file but did not do a save as Unicode.
> When I did the Save As Unicode, the file imported correctly.
> Thanks for your help.
>
>> Aaah, did not realize you were using PBDOM... Well,
>> PBDOM_Builder always uses UTF-16LE Encoding. One thing
>> you need to make sure of is that the document, if
>> declared as UTF-16LE is actually saved in that format (and
>> not as simple ASCII Text), a tool like TextPad will help
>> you determine the actual encoding of the document, and
>> allow you to encode it differently if necessary. Beyond
>> making sure that the encoding is correct, since that's the
>> major change from PB 9 and PB 10 and above is the ASCII /
>> Unicode barrier, I'm not sure where to go from there,
>> maybe someone else will be able to pick this up and be
>> helpful.
>>
>> --
>> Dave Hauze
>>
>> <Kevin Arnold> wrote in message
>> news:49a70fa2.6e2b.1681692777@sybase.com... >I am not
>> > doing a string manipulation, I am reading the XML into
>> the PBDOM_Builder and then get the GetParseErrors. >
>> > lpbdom_bldr = Create PBDOM_Builder
>> > lpbdom_doc =
>> > lpbdom_bldr.BuildFromFile(is_xml_file_location)
>> lb_bad_parse = lpbdom_bldr.GetParseErrors(ls_parse_errors)
>> > >> This may have to do with the switch from ASCII to
>> Unicode. >> There are some enumerations for string and
>> blob functions >> that you can use to properly format the
>> XML string (in >> addition, in the .XML header, what
>> format is specified, >> example below).
>> >>
>> >> You might see:
>> >> <?xml version="1.0" encoding="ASCII" standalone="yes"?>
>> >>
>> >> Or for Unicode
>> >> <?xml version="1.0" encoding="UTF-16LE"
>> standalone="yes"?> >> or
>> >> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>> >>
>> >> Depending on which one is being used you may need to
>> use >> the enumerations "EncodingANSI!" or
>> "EncodingUTF16LE!" or >> "EncodingUTF8!"
>> >>
>> >> Hope this helps!
>> >>
>> >> --
>> >> Dave Hauze
>> >>
>> >> <Kevin Arnold> wrote in message
>> >> > news:49a56e69.3f0c.1681692777@sybase.com... We
>> recently >> > upgraded from PB 9 to PB 11.5 and when
>> importing an XML >> > file into our app, we get an error
>> calling >> > GetParseErrors. The error states the "degree
>> symbol" is >> > illegal. This same XML file worked fine in
>> PB 9, but now >> does not. Anyone know what I can do to
>> fix this? > >> > Thanks,
>> >> > Kevin
>> >>
>> >>
>>
>>


Kevin Arnold Posted on 2009-02-26 19:59:53.0Z
Sender: 4665.49a5aa7c.1804289383@sybase.com
From: Kevin Arnold
Newsgroups: sybase.public.powerbuilder.xml
Subject: Re: Data Format Exception
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <49a6f4b9.69ed.1681692777@sybase.com>
References: <49a56e69.3f0c.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 26 Feb 2009 11:59:53 -0800
X-Trace: forums-1-dub 1235678393 10.22.241.41 (26 Feb 2009 11:59:53 -0800)
X-Original-Trace: 26 Feb 2009 11:59:53 -0800, 10.22.241.41
Lines: 13
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.xml:1805
Article PK: 814346

I was able to find a fix to my issue. The encoding was set
to UTF-8 and when we changed to iso-8859-1, the file
imported with no issues. Don't know why, but that seemed to
fix it for us.

> We recently upgraded from PB 9 to PB 11.5 and when
> importing an XML file into our app, we get an error
> calling GetParseErrors. The error states the "degree
> symbol" is illegal. This same XML file worked fine in PB 9
> , but now does not. Anyone know what I can do to fix this?
>
> Thanks,
> Kevin