Symptom
- Some special characters within a SQL statement are converted into a control character (0x1A).
- When the table already contains such a special character, it can be shown in Interactive SQL result set, using a SELECT statement.
- For example using Interactive SQL, a special character cannot be stored into a table using the following statement:
INSERT INTO <table> (<column>) VALUES ('<special character>')
This issue may occur when trying to call the OpenXML procedure within a PowerBuilder application using a statement like the following:
SQLCA.SyntaxFromSQL("SELECT ... FROM OPENXML( '<XML document containing special characters>', ...
The execution of this statement causes the error: 'XML parser error: character: <character pos>, line: <line number>, column: <column number> Illegal control character'
Read more...
Environment
- SAP SQL Anywhere 16
SAP SQL Anywhere 12
Sybase SQL Anywhere 11
Sybase SQL Anywhere 10
Product
SAP SQL Anywhere all versions ; Sybase SQL Anywhere 10.0 ; Sybase SQL Anywhere 11.0
Keywords
KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.