Skip to main content

Qlik

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable
‎2018-11-23 03:48 AM

Qlik Sense - After November 2018 update CodePage does not work

Hello everyone,

I have problem with my ODBC string connection and character encoding. I had this:

 

ODBC CONNECT TO [host_name] (XUserId is XXXXXXXXXXXXXXXXXXX, XPassword is XXXXXXXXXXXXXXXXXXX, CodePage is 28592);

Everything worked well, but after being updated to November 2018 CodePage does not work. 

How I can fix it? 

 

349 Views
0 Likes
2 Replies
Anil_Babu_Samineni
MVP
MVP
‎2018-11-23 04:17 AM

What version you were earlier? Looks like this version used for Qlikview. Seems, You are with very old version.
Best Anil, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful
338 Views
Anonymous
Not applicable
‎2018-11-23 04:26 AM
Author

In response to Anil_Babu_Samineni

Our company migrated to Qlik Sense Server September 2018 verion from Qlik View 12.10. We convert our reports and we turn off standard mode (for legacy mode). On version September 2018 we had no problems with character encoding. 

Yesterday I made the upgrade to the November 2018 (+ patch 1) version and now we have a problem with character encoding. We did not change anything in the scripts.

331 Views
0 Likes