Upper case access verify codes

[Matthew King]

Although the access and verify codes are usually case insensitive,

there is one exception. That is when you must (or decide to) change
your verify code, then you must start your login with your original
access/verify code in UPPER CASE. If you don't do this, VistA will not
accept your code change even if you switch to caps to do it.

[Sam Habiel]

The whole case sensitivity issue is broken, in my opinion. You have
to use UPPER case, even though it tells you to do mixed case. It
always confuses me. Someone needs to do a survey of all the places
that a code is asked for, and check each one out.

Kevin

On Oct 29, 6:25 pm, Sam Habiel <sam.hab...@…> wrote:
Some may not even argue that this is a bug at all...

GTM>D CVC^{KBANDemo(1)
Current Code: CATDOG.77
New Code 1: Indigo.33
New Code 2: Indigo.33
ret(0)=1
ret(1)="Enter 8-20 characters mixed alphanumeric and punctuation (except '}', ';

', ':')."

GTM>D ^XPAREDIT

--- Edit Parameter Values ---

Select PARAMETER DEFINITION NAME: XU VC CASE SENSITIVE Verify Code is case
sensitive

---

Enable Verify Code case sensitive: YES <enter>

GTM>D CVC^{KBANDemo(1)
Current Code: CATDOG.77
New Code 1: Indigo.33
New Code 2: Indigo.33
ret(0)=0
ret(1)=""}

So what's the bug?
When you are changing the verify code via the published RPC in
CVC^{XUSRB, and you don't use a total uppercase VC, and XU VC CASE
SENSITIVE is false for the system, you get a non-descript error
message that doesn't explain the reason for failure. If you change
your verify code using the DD code in fileman (i.e. the normal way you
do so inside Vista), it automatically converts it to uppercase
provided that XU VC CASE SENSITIVE is false. I am tried of testing all
the possibilities, so I hope somebody can play some more.}

Sam