I've been investigating an issue migrating our 10.5 apps which use rich text edits and save data to a SQL Anywhere 12 database on a long nvarchar column.
It works perfectly in 10.5 but in 12.6 the text written to the database is modified during the update to replace an embedded \n to a carriage return. I note that this is the case with the same ODBC connection to the same database - illustrating it is not an SA issue - but possibly a datawindow issue.
This results in the rich text returning to the RichTextEdit from the database looking like it has a a prefix "owidctlpar".
This is actually the corruption of the rich text control string segment string itap0\nowidctlpar where the \n is converted to a CR
Apparently this has been reported before as an issue and users have been told to set DisableBind=0 or convert the column to a long binary. Neither of these are an option for us. Apparently these fixes get around the problem (unfortunately neither a workable solution for us) - but there remains the following question.
Since the source to the column could be anything (not necessarily rich text) - could PB 12.6 be corrupting any long nvarchar (or nvarchar) data which contains an embedded "\n"???
I have sent test cases of this to SAP support - but I want the community to recognize that there could be a broader problem affecting those not using datawindows to store rich text.
Glenn