Changing case problem

Question

I need to turn data entered by user in a form to upper case, but accents are displayed incorrectly if I set item property "case restriction" to upper.
The same happen if I run the following in Sql Plus:
SQL> select upper('Informações') from dual;
UPPER('INFO
INFORMAGUES
My nls_language seems to be set correctly:
SQL> SELECT * FROM NLS_SESSION_PARAMETERS;
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
PARAMETER VALUE
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZH:TZM
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZH:TZM
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
Any thoughts?

Answer 1

Hi joep,
This question slightly related to another Q I answered earlier today. Pleas tak a look at this answer.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HFORCEKWTID=82263:5&HOID=50650000000800000016B20000&HExpertOnly=&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0
I said slightly, not exactly!
What is going on (I suspect) is that you deleting or re-arranging enums and the definition of "string to value"s is not matching up with the case structure. This happens when a enum that is NOT a typedef is wired to the selector.
A typedef is a construct that can be used to DEFine a data TYPE. An example of a data type that you may want to define is the relationships between the strings and the numeric values in a enum.
By defining a type
def, LV will check to make sure the definitions of of strings to values will be consitant throught your code.
You can create a typedef by first selecting the enum control and doing a "right-click>>>advanced>>>customize".
Once in the control editor, change the drop-down menu on the tool bar from its default value of "control" to "Type Def.". Save the control, and answer yes to the replace question.
Then go back to your code and replace all of the non-typdef'd nodes etc with the control you saved.
Once you do this, LV should be able to keep all of your cases matched up. If you make a change that could cause incorrect operation, your run arrow will break alerting you to the issue (provided you do not define a default case).
I hope this help,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction