Textbox - Database driven Auto-Complete & Unicode fails

[t.s.h]

If I add a textbox with an DB-Driven Autocomplete to my form and I choose a unicode field from the database for the "choice options field" I get no suggestions.
If I change the "choice option field" to a char or numeric field from the database everything works fine.
The "choices values field" is a 8,0 dec. field from the database, the bind value field is also 8,0 dec.

Could someone help me with this issue?

[David]

We can recreate this problem here. We are investigating a solution.

[David]

We have found the cause of the problem and corrected it for the next update to Profound UI, 3.1.5.

[t.s.h]

thanks, you guys are really fast!

[t.s.h]

I have installed 3.1.5 now, and it works partially now. :o(
Latin letters and number are shown now, but japanese chars in example are not displayed in a combo or dropdownbox. It seems not to be an issue of the selected font cause the data is displayed with the same font in a "output only" textbox without database selection.
So i guess something in the SQL goes wrong....

If you wish I could provide you a example table containing some special unicode chars like cyrillic or japanese.

[David]

I think I understand why it's doing this.

The database has the option of giving the data in either the job EBCDIC code page or Unicode. Currently, we ask for the data in job EBCDIC code page. The problem before was that this is often set to 65535 which was causing the original problem. We've changed it so that it uses the correct http server CCSID.

But, this means that the support for Unicode is incomplete as not all characters can be represented in a single EBCDIC CCSID. This is why only the Latin characters are working for you. If the http server CCSID was set for Japanese, then those would work for you.

The long term solution will be to change the process so that it deals in the data in Unicode, rather than EBCDIC. This will allow for all characters to work properly, but will take us some time to implement.

[YehudaV]

I'm also interested for this solution :)

[t.s.h]

After a long, long time....Are there any news about this issue?
Changing the server CCSID to Japanese does not bring the solution we need.
Because we have also mixed chars in some names or titles i.e. katakana and cyrillic.

[Scott Klement]

Please file a feature request with Profound Logic so that this can be added to the list of enhancements that we are considering.

To file a feature request, send an e-mail to support@profoundlogic.com