I have an Alpha Five v11 web application application that includes nvarchar() fields in the SQL server database. These fields contain Chinese characters.
When I view these fields in a Grid component, the characters are correctly displayed.
However, when I put them in a report, they are displayed as "??????"
Here's what I think is happening: Since the report is, at the most basic level, a desktop component, the data from the SQL server is being inserted into a temporary Alpha Five database. This seems to be indicated by the dialog box when you override field definitions when you are creating the report's SQL data source definition. I believe that the report then runs against that temporary database to generate the output. (This is all just a guess on my part as to how this is working behind the scenes)
Many posts here on the messageboard indicate that the desktop database won't support UTF-8 or other extended character sets, so I'm guessing that the Chinese characters are being lost in this database translation.
So, my questions:
1. Is this correct? Or am I missing something that would permit me to display Chinese characters from a SQL server database in a field on a report in a web application?
2. Can you recommend a work-around to make this work? While Chinese is my immediate issue, I will be dealing with a dozen other languages in the next few months.
Thank you for your help!
-Mark
When I view these fields in a Grid component, the characters are correctly displayed.
However, when I put them in a report, they are displayed as "??????"
Here's what I think is happening: Since the report is, at the most basic level, a desktop component, the data from the SQL server is being inserted into a temporary Alpha Five database. This seems to be indicated by the dialog box when you override field definitions when you are creating the report's SQL data source definition. I believe that the report then runs against that temporary database to generate the output. (This is all just a guess on my part as to how this is working behind the scenes)
Many posts here on the messageboard indicate that the desktop database won't support UTF-8 or other extended character sets, so I'm guessing that the Chinese characters are being lost in this database translation.
So, my questions:
1. Is this correct? Or am I missing something that would permit me to display Chinese characters from a SQL server database in a field on a report in a web application?
2. Can you recommend a work-around to make this work? While Chinese is my immediate issue, I will be dealing with a dozen other languages in the next few months.
Thank you for your help!
-Mark
Comment