Case statement doesn't work correctly

[Cecil]

I put in a couple watches, such as strSvcType and LEN(strSvcType). strSvcType equals "HOL". The string length of the variable, strSvcType is 3. As I was stepping through the code, I saw that the strSvcType variable was "HOL" (sorry for being a bit redundant here), yet the program did not go into that case; it completely bypassed it. Is there some bug in MS Access that causes it to bypass a CASE statement where the value of the variable is correct, yet the Case seems to ignore it? Or, did I miss something?

A little later: I just received a Skype call from a friend about this. he told me to remove the strSvcType = from the Case and just have Case "HOL". Well, this is way different from Visual FoxPro. I do hope it works.



Select Case strSvcType
Case strSvcType = "HOL"
strsql = strsql & "'" & strDOS & "', "
strsql = strsql & "'BG', "
strsql = strsql & "'BG', "

Case strSvcType = "PAC"
strsql = strsql & "'12/31/2999', "
strsql = strsql & "'BG', "
strsql = strsql & "'BG', "

[ranman256]

ive never seen it skip it, but you are redundant
The select case statement watches the variable
you don't have to utilize that variable again...

Select Case strSvcType
        Case  "HOL"
        case "PAC"
end select

[Micron]

You would only use operators if you want to compare against numeric values.
Case Is > 9
Case Is = 9 - works, but is a bit redundant. Case 9 might be better.
Case 5 To 9 - either 5,6,7,8 or 9 should cause this to be selected.

Re: '12/31/2999' - does this actually work? You are delimiting what looks like a date as though it were a string.

[Cecil]

I had a friend call me and tell me that I didn't need the redundancy. You are both right. Thanks Ranman256.