Where Query does not allow me to use Or to include two possible entries in field

[Ed Bitzer]

I have been programming in access for over 30 years but the brain is apparently fading at age 92. This where cause and I quote "WHERE (((SECURITY.SecType)="S" Or (SECURITY.SecType) = "E"));" works fine in a test query created in the designer but when created in a subroutine and executed it displays the "Error" that the where cause should stop after the first criteria. I just will not handle "OR". Now my old thinking is no matter what the quoted letter is the query should work, just not find that letter in my table. However the table does have both E's and S's.




Now hopefully I am just an old guy that has forgot some obvious syntax difference from that created by the designer and that required when executed in code. On the other hand, you may require that I include the entire query which is a simple Select query.


Appreciate,


Ed

[Welshgasman]

Show your code!

[madpiet]

Oh help. Abscess and it's love for parentheses.

WHERE SECURITY.SecType="S" Or SECURITY.SecType = "E"

or
WHERE Security.SecType IN ("S","E")

[davegri]

If you're creating this as an SQL string, those double quotes around embedded strings will be a problem. Do it this way with single quotes:
WHERE SECURITY.SecType='S' Or SECURITY.SecType = 'E'

[Ed Bitzer]

Thanks guys. I have a weak excuse to not thanking you for the clue needed to solve this problem which was a simple as remember that SQL statements require handling variables and constants differently than that created by the "Designer." I had to add the necessary extra single quote followed by the regular quote and an & symbol. The excuse I was off on in the ER for a gushing nosebleed four times before they finally handled by cauterizing.

[ArviLaanemets]

Anyway, I'd advice you ise IN() instead of all those OR's (like Madpiet posted).
Reasons:
a) You avoid bloating your querystring (no problem with current 2 values, but why use different syntax for same thing when in future you need more of them listed in some query);
b) You can use same syntax to use table or query instead of value list. Like
IN(SomeTable)
or
IN(SomeSavedQuery)
or
IN(SELECT...)