Hi,
I keep getting a 'runtime error 13 type mismatch' error when running a macro in excel 2003 SP3, i cant see nothing wrong with the scripting when i click on 'debug' can anyone spot what i am doing wrong ? here is the higlighted error
i am running windows xp sp3 and office version 2003 sp3
please see below
------------------------------------------------
Please Login or Register to view this content.
Last edited by Leith Ross; 12-21-2009 at 12:14 PM. Reason: Added Code Tags
From my testing, you can not refer to a named range which includes multiple cells in a conditional statement. You have to specify which cell you want to test.
In this example, I've referenced the first cell in the range (which I set as a multidimensional named range on the sheet).Please Login or Register to view this content.
Hi
It depends upon the value of the range being compared, e.g. comparing a number to a string will throw an error, or if the range has an error value that will cause an error to show as well.
What are the value of the ranges being compared?
Regards
Jeff
i didnt actually write this i'm trying to solve a company problem
this is the error thats thrown up, the problem is that some users can use it fine and other other get the run time error
Hello selbo81.
To make your posts easier to read, copy, and edit please wrap your code. I did it for you this time. Here is how you can do it next time.
How to wrap your Code
1. Select all your code using the mouse.
2. Click on the # icon on the toolbar in the Message window. This will automatically wrap the text you selected with the proper Code tags to create a Code Window in your post.
3. To do it manually...
Use the Bulletin Board Code Tags
[code]Please [url=https://www.excelforum.com/login.php]Login or Register [/url] to view this content.[/code] at the end of the last line.
To learn more about BB codes used in this forum, just click on the link below...
Bulletin Board Codes Tags
Sincerely,
Leith Ross
Remember To Do the Following....
1. Use code tags. Place [CODE] before the first line of code and [/CODE] after the last line of code.2. Thank those who have helped you by clicking the Starbelow the post.
3. Please mark your post [SOLVED] if it has been answered satisfactorily.
Old Scottish Proverb...
Luathaid gu deanamh maille! (Rushing causes delays!)
now no one can see what part of the code is wrong ??? i highlighted it in bold before
Last edited by selbo81; 12-21-2009 at 12:30 PM.
I posted an entire post, with the most likely explanation. Another poster added an alternative reason why it would fail.Originally Posted by selbo81
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
Bookmarks