Why do ODBC diagnostic text and result-sets output in XML contain garbage characters?

Easysoft XML-ODBC Server

Why do ODBC diagnostic text and result-sets output in XML contain garbage characters?

Article :	00702
Last Reviewed :	19th July 2005
Revision :	1

The usual reason for this is that you are using a version of the
unixODBC driver manager prior to 2.2.2 which had some UNICODE
problems. UNICODE was always expected big endian and always converted
to big endian whereas it should have been native endianess.

All versions of XML-ODBC contain at least unixODBC 2.2.2 and should
not have this problem but you may have elected to use an existing
installation of unixODBC when you installed XML-ODBC. If this is the
case re-run the XML-ODBC installation and select to install the
included unixODBC and then make sure your dynamic linker picks up this
version before your existing version.

Applies To

Products
- Easysoft XML-ODBC Server

*	Did this content help you? Yes No Maybe

*	Please select one option based on your first choice: I'm very satisfied I think it will help, but I haven't tried it yet It is helpful, but I need more information It is helpful, but hard to understand Seemed relevant in search results, but didn't help me The information is incorrect The page contains one or more broken links

	Suggest new content or let us know how we can improve this content:

	(* Required Fields)

Easysoft XML-ODBC Server

Why do ODBC diagnostic text and result-sets output in XML contain garbage characters?

Applies To

Knowledge Base Feedback