I am stumped. The code below works fine until it hits the "#N/A". It then gives Run Type Error 13 Type Mismatch.
The column with the #N/A has been converted from vlookup to values so wouldn't it just be a string like the rest?
Why is it doing that and how do I stop it?
Please Login or Register to view this content.Please Login or Register to view this content.
VBA cannot handle #N/A responses
you need to tell it what to do with the error
some light reading for you
http://www.cpearson.com/excel/errorhandling.htm
easiest way to bypass this is by putting
**caveatPlease Login or Register to view this content.
It is tempting to deal with errors by placing an On Error Resume Next statement at the top of the procedure in order to get the code to run without raising an error. This is very bad coding practice. Remember that using On Error Resume Next does not fix errors. It merely ignores them.
If you are satisfied with the solution(s) provided, please mark your thread as Solved.
Select Thread Tools-> Mark thread as Solved. To undo, select Thread Tools-> Mark thread as Unsolved.
Perhaps this
Please Login or Register to view this content.
Last edited by xlnitwit; 05-22-2017 at 03:32 AM. Reason: Correct code!
Don
Please remember to mark your thread 'Solved' when appropriate.
@ xlnitwit
Think you need to change lRow to n in your For .... Next loop. Also End If might work better.
Please Login or Register to view this content.
Avoid using Select, Selection and Activate in your code. Use With ... End With instead.
You can show your appreciation for those that have helped you by clicking the * at the bottom left of any of their posts.
Done- thank you! The dangers of trying to reply from a phone.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
Bookmarks