Test for Error in cells

  • Thread starter Thread starter LeeL
  • Start date Start date
L

LeeL

I am trying to test for letters or numbers within a cell.
I cannot get the Iserror to work correctly, nonerror is ok, but if it is an
error, i cannot get True, i get a VBA error.

Can someone please help?

a1$ = Mid(Range("a1").Text, 2, 1)
b1$ = Mid(Range("b1").Text, 3, 1)
If IsError(a1 * b1) Then
MsgBox "error"
Else: MsgBox "nonerror"
End If
 
Does this code do what you want?

a1$ = Mid(Range("a1").Text, 2, 1)
b1$ = Mid(Range("b1").Text, 3, 1)
If a1$ Like "#" And b1$ Like "#" Then
MsgBox "Two numbers"
Else
MsgBox "Error"
End If

If not, I think you will need to provide more information about what is in
A1 and B1 and what you actually want to do with them.
 
Yes it does- Thanks!

I also got it working using IsNumericand Not IsNumeric.

Like "#" 'is testing for a number, is there a similar way to test for a
letter.
 
LeeL said:
I am trying to test for letters or numbers within a cell.
I cannot get the Iserror to work correctly, nonerror is ok, but if it is an
error, i cannot get True, i get a VBA error.

Can someone please help?

a1$ = Mid(Range("a1").Text, 2, 1)
b1$ = Mid(Range("b1").Text, 3, 1)
If IsError(a1 * b1) Then
MsgBox "error"
Else: MsgBox "nonerror"
End If


Sub test()
Dim a1$, b1$, v

a1$ = Mid(Range("a1").Text, 2, 1)
b1$ = Mid(Range("B1").Text, 3, 1)

'....
On Error Resume Next

v = a1$ * b1$

If Err Then
Err.Clear
MsgBox "Error"
Else
MsgBox "Not Error"
End If

On Error GoTo 0

End Sub

regards
r

Il mio ultimo lavoro ...
http://excelvba.altervista.org/blog/index.php/Excel-VBA/UsedRange-eccezioni-e-alternative.html
 
This will test for an upper case letter...

If a1$ Like "[A-Z]" Then

This will test for a lower case letter...

If a1$ Like "[a-z]" Then

And this will test for a letter no matter what its case is...

If a1$ Like "[A-Za-z]" Then

Of course, the Like operator can do far more than testing for single
characters. If you are interested in seeing what else it can do, put your
cursor on the keyword Like in any place it is used in your code and then
press the F1 key. By the way, for single digit checking, IsNumeric is okay
to use; however, you might want to consider the following previous posting
of mine if you ever intend to use it for checking multiple digits...

I usually try and steer people away from using IsNumeric to "proof"
supposedly numeric text. Consider this (also see note below):

ReturnValue = IsNumeric("($1,23,,3.4,,,5,,E67$)")

Most people would not expect THAT to return True. IsNumeric has some "flaws"
in what it considers a proper number and what most programmers are looking
for.

I had a short tip published by Pinnacle Publishing in their Visual Basic
Developer magazine that covered some of these flaws. Originally, the tip was
free to view but is now viewable only by subscribers.. Basically, it said
that IsNumeric returned True for things like -- currency symbols being
located in front or in back of the number as shown in my example (also
applies to plus, minus and blanks too); numbers surrounded by parentheses as
shown in my example (some people use these to mark negative numbers);
numbers containing any number of commas before a decimal point as shown in
my example; numbers in scientific notation (a number followed by an upper or
lower case "D" or "E", followed by a number equal to or less than 305 -- the
maximum power of 10 in VB); and Octal/Hexadecimal numbers (&H for
Hexadecimal, &O or just & in front of the number for Octal).

NOTE:
======
In the above example and in the referenced tip, I refer to $ signs and
commas and dots -- these were meant to refer to your currency, thousands
separator and decimal point symbols as defined in your local settings --
substitute your local regional symbols for these if appropriate.

As for your question about checking numbers, here are two functions that I
have posted in the past for similar questions..... one is for digits only
and the other is for "regular" numbers:

Function IsDigitsOnly(Value As String) As Boolean
IsDigitsOnly = Len(Value) > 0 And _
Not Value Like "*[!0-9]*"
End Function

Function IsNumber(ByVal Value As String) As Boolean
' Leave the next statement out if you don't
' want to provide for plus/minus signs
If Value Like "[+-]*" Then Value = Mid$(Value, 2)
IsNumber = Not Value Like "*[!0-9.]*" And _
Not Value Like "*.*.*" And _
Len(Value) > 0 And Value <> "." And _
Value <> vbNullString
End Function

Here are revisions to the above functions that deal with the local settings
for decimal points (and thousand's separators) that are different than used
in the US (this code works in the US too, of course).

Function IsNumber(ByVal Value As String) As Boolean
Dim DP As String
' Get local setting for decimal point
DP = Format$(0, ".")
' Leave the next statement out if you don't
' want to provide for plus/minus signs
If Value Like "[+-]*" Then Value = Mid$(Value, 2)
IsNumber = Not Value Like "*[!0-9" & DP & "]*" And _
Not Value Like "*" & DP & "*" & DP & "*" And _
Len(Value) > 0 And Value <> DP And _
Value <> vbNullString
End Function

I'm not as concerned by the rejection of entries that include one or more
thousand's separators, but we can handle this if we don't insist on the
thousand's separator being located in the correct positions (in other words,
we'll allow the user to include them for their own purposes... we'll just
tolerate their presence).

Function IsNumber(ByVal Value As String) As Boolean
Dim DP As String
Dim TS As String
' Get local setting for decimal point
DP = Format$(0, ".")
' Get local setting for thousand's separator
' and eliminate them. Remove the next two lines
' if you don't want your users being able to
' type in the thousands separator at all.
TS = Mid$(Format$(1000, "#,###"), 2, 1)
Value = Replace$(Value, TS, "")
' Leave the next statement out if you don't
' want to provide for plus/minus signs
If Value Like "[+-]*" Then Value = Mid$(Value, 2)
IsNumber = Not Value Like "*[!0-9" & DP & "]*" And _
Not Value Like "*" & DP & "*" & DP & "*" And _
Len(Value) > 0 And Value <> DP And _
Value <> vbNullString
End Function
 
Thank you very much for all the examples! And very glad I mentioned the
IsNumeric and you pointed out the flaws. I will use Like "[A-Za-z]" and Like
"#", I'm sure this will will save me from headaces the IsNumeric would create!
--
Thanks & Best Regards


Rick Rothstein said:
This will test for an upper case letter...

If a1$ Like "[A-Z]" Then

This will test for a lower case letter...

If a1$ Like "[a-z]" Then

And this will test for a letter no matter what its case is...

If a1$ Like "[A-Za-z]" Then

Of course, the Like operator can do far more than testing for single
characters. If you are interested in seeing what else it can do, put your
cursor on the keyword Like in any place it is used in your code and then
press the F1 key. By the way, for single digit checking, IsNumeric is okay
to use; however, you might want to consider the following previous posting
of mine if you ever intend to use it for checking multiple digits...

I usually try and steer people away from using IsNumeric to "proof"
supposedly numeric text. Consider this (also see note below):

ReturnValue = IsNumeric("($1,23,,3.4,,,5,,E67$)")

Most people would not expect THAT to return True. IsNumeric has some "flaws"
in what it considers a proper number and what most programmers are looking
for.

I had a short tip published by Pinnacle Publishing in their Visual Basic
Developer magazine that covered some of these flaws. Originally, the tip was
free to view but is now viewable only by subscribers.. Basically, it said
that IsNumeric returned True for things like -- currency symbols being
located in front or in back of the number as shown in my example (also
applies to plus, minus and blanks too); numbers surrounded by parentheses as
shown in my example (some people use these to mark negative numbers);
numbers containing any number of commas before a decimal point as shown in
my example; numbers in scientific notation (a number followed by an upper or
lower case "D" or "E", followed by a number equal to or less than 305 -- the
maximum power of 10 in VB); and Octal/Hexadecimal numbers (&H for
Hexadecimal, &O or just & in front of the number for Octal).

NOTE:
======
In the above example and in the referenced tip, I refer to $ signs and
commas and dots -- these were meant to refer to your currency, thousands
separator and decimal point symbols as defined in your local settings --
substitute your local regional symbols for these if appropriate.

As for your question about checking numbers, here are two functions that I
have posted in the past for similar questions..... one is for digits only
and the other is for "regular" numbers:

Function IsDigitsOnly(Value As String) As Boolean
IsDigitsOnly = Len(Value) > 0 And _
Not Value Like "*[!0-9]*"
End Function

Function IsNumber(ByVal Value As String) As Boolean
' Leave the next statement out if you don't
' want to provide for plus/minus signs
If Value Like "[+-]*" Then Value = Mid$(Value, 2)
IsNumber = Not Value Like "*[!0-9.]*" And _
Not Value Like "*.*.*" And _
Len(Value) > 0 And Value <> "." And _
Value <> vbNullString
End Function

Here are revisions to the above functions that deal with the local settings
for decimal points (and thousand's separators) that are different than used
in the US (this code works in the US too, of course).

Function IsNumber(ByVal Value As String) As Boolean
Dim DP As String
' Get local setting for decimal point
DP = Format$(0, ".")
' Leave the next statement out if you don't
' want to provide for plus/minus signs
If Value Like "[+-]*" Then Value = Mid$(Value, 2)
IsNumber = Not Value Like "*[!0-9" & DP & "]*" And _
Not Value Like "*" & DP & "*" & DP & "*" And _
Len(Value) > 0 And Value <> DP And _
Value <> vbNullString
End Function

I'm not as concerned by the rejection of entries that include one or more
thousand's separators, but we can handle this if we don't insist on the
thousand's separator being located in the correct positions (in other words,
we'll allow the user to include them for their own purposes... we'll just
tolerate their presence).

Function IsNumber(ByVal Value As String) As Boolean
Dim DP As String
Dim TS As String
' Get local setting for decimal point
DP = Format$(0, ".")
' Get local setting for thousand's separator
' and eliminate them. Remove the next two lines
' if you don't want your users being able to
' type in the thousands separator at all.
TS = Mid$(Format$(1000, "#,###"), 2, 1)
Value = Replace$(Value, TS, "")
' Leave the next statement out if you don't
' want to provide for plus/minus signs
If Value Like "[+-]*" Then Value = Mid$(Value, 2)
IsNumber = Not Value Like "*[!0-9" & DP & "]*" And _
Not Value Like "*" & DP & "*" & DP & "*" And _
Len(Value) > 0 And Value <> DP And _
Value <> vbNullString
End Function
 
Back
Top