Forum Discussion
QuickBaseCoachD
8 years agoQrew Captain
I don't know of an all encompassing guide, but I believe when the test is for equals, such as
If([Status]="shipped",
.. then the test is case specific.
But
if(Contains([Status], "shipped"), ...
is not case sensitive.
I know that report filters are not case sensitive, nor are summary field filters.
Since case ( , ) is essentially a test on Equals, then it is case sensitive.
So my rule of thumb is that for formulas testing equals or Case, then it is case sensitive, else not case sensitive in other situations.
There has been times where is Used UPPER to ensure a match.
such as if(Upper([Status]) = "SHIPPED", true...
so I convert my data to upper case and then test against an Upper Case string.
If([Status]="shipped",
.. then the test is case specific.
But
if(Contains([Status], "shipped"), ...
is not case sensitive.
I know that report filters are not case sensitive, nor are summary field filters.
Since case ( , ) is essentially a test on Equals, then it is case sensitive.
So my rule of thumb is that for formulas testing equals or Case, then it is case sensitive, else not case sensitive in other situations.
There has been times where is Used UPPER to ensure a match.
such as if(Upper([Status]) = "SHIPPED", true...
so I convert my data to upper case and then test against an Upper Case string.
- _anomDiebolt_8 years agoQrew Elite>so I convert my data to upper case
lower case is better as you don't have to hit the shift key.
Trivia: Believe it or not this is why most JavaScript programmer prefer single quote over double quotes - to save a keystoke. This is the one commonplace style convention I have not adopted when writing JavaScript because of a ton of Tcl code I wrote earlier in my career where single and double quotes effected interpolation. - QuickBaseCoachD8 years agoQrew CaptainOK, that tip should push out my onset of carpel tunnel syndrome by an hour or so sometime in the future and increase my billing efficiency. _