Easysoft XML-ODBC Server

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

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. All versions of XML-ODBC contain at least unixODBC 2.2.2. However, you may have chosen to use an existing unixODBC installation, instead of the one distributed with XML-ODBC. If this is the case, re-run the XML-ODBC installation, and select to install unixODBC. Then make sure your dynamic linker picks up this version before your existing version.

Applies To

• Products
  • Easysoft XML-ODBC Server

Knowledge Base Feedback

* 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)

• About Easysoft

• Contact Us
• About Us
• Clients
• Upgrade Offer
• Blog
• Careers

• Products

• ODBC Drivers
• JDBC Drivers
• Bridges and Gateways
• In Development

• Services

• Consultancy
• Training
• Custom Development

• Licensing

• Product Licenses
• Prices

• Support

• Support Home
• Solution Wizard
• Getting Started Guides
• User Guides
• Knowledge Base

• Search

• Easysoft.com
• Documentation
• Knowledge Base

• Popular Resources

• Developer Area
• Client Applications

• Legal

• Privacy Statement

© 1993 - 2024 Easysoft Limited. All rights reserved. Oracle® is a registered trademark of Oracle® Corporation and/or its affiliates. Other trademarks and registered trademarks appearing on easysoft.com are the property of their respective owners.

• 
• 
• 
•