Here is a quick tip to start the week.
Often, we end up with a situation where a bunch of numbers are stored as text.
In such cases, Excel displays a warning indicator at the top-left corner of the cell. If you click on warning symbol next to the cell, Excel shows a menu offering choices to treat the error.
Converting numbers stored as text back to numbers
Tip #1: Error correction
One easy and quick way to convert all the text-numbers to numbers is,
- Select all the cells
- Click on warning indicator next to top-most cell
- Choose Convert to number option
- Done
Tip#2: Paste Special Convert
Sometimes such text-numbers may be scattered across the worksheet, thus making selection of cells a pain.
In such cases, follow this process (see demo below)
- In a blank cell, just type 1
- Copy this blank cell.
- Select all the cells that have text-numbers.
- Press CTRL+ALT+V to launch Paste Special box.
- Choose Multiply from operation area.
- Click ok & Done!
Enjoy your numbers.
Bonus tip: If you think the error indicators are annoying, you can turn them off. Just go to File > Options > Formulas and turn off all the error checking rules you don’t need.
PS: Thanks to Justin for emailing me the Paste Special Multiply with 1 trick.
6 Responses to “Make VBA String Comparisons Case In-sensitive [Quick Tip]”
Another way to test if Target.Value equal a string constant without regard to letter casing is to use the StrCmp function...
If StrComp("yes", Target.Value, vbTextCompare) = 0 Then
' Do something
End If
That's a cool way to compare. i just converted my values to strings and used the above code to compare. worked nicely
Thanks!
In case that option just needs to be used for a single comparison, you could use
If InStr(1, "yes", Target.Value, vbTextCompare) Then
'do something
End If
as well.
Nice tip, thanks! I never even thought to think there might be an easier way.
Regarding Chronology of VB in general, the Option Compare pragma appears at the very beginning of VB, way before classes and objects arrive (with VB6 - around 2000).
Today StrComp() and InStr() function offers a more local way to compare, fully object, thus more consistent with object programming (even if VB is still interpreted).
My only question here is : "what if you want to binary compare locally with re-entering functions or concurrency (with events) ?". This will lead to a real nightmare and probably a big nasty mess to debug.
By the way, congrats for you Millions/month visits 🙂
This is nice article.
I used these examples to help my understanding. Even Instr is similar to Find but it can be case sensitive and also case insensitive.
Hope the examples below help.
Public Sub CaseSensitive2()
If InStr(1, "Look in this string", "look", vbBinaryCompare) = 0 Then
MsgBox "woops, no match"
Else
MsgBox "at least one match"
End If
End Sub
Public Sub CaseSensitive()
If InStr("Look in this string", "look") = 0 Then
MsgBox "woops, no match"
Else
MsgBox "at least one match"
End If
End Sub
Public Sub NotCaseSensitive()
'doing alot of case insensitive searching and whatnot, you can put Option Compare Text
If InStr(1, "Look in this string", "look", vbTextCompare) = 0 Then
MsgBox "woops, no match"
Else
MsgBox "at least one match"
End If
End Sub