Type Mismatch on Superscript

[jomili]

The code below has been in place for about a year, as part of a daily routine. This morning it started giving me a "Run-time error 13: Type Mismatch" on the line in red in the code below. I've attached the worksheet the macro works on, but I can't understand why it's giving an error. Your help is appreciated.

Please Login or Register  to view this content.

[JapanDave]

It is deffinitly not liking this in Range("E115")

Please Login or Register  to view this content.

Why not do something like this , as it does not seem to do anything with that row anyway?

Please Login or Register  to view this content.

[jomili]

Thanks JapanDave.

I wondered if that Value error was the cause of my problem. I'll need to research and see where that came from.

The error handling I'll use (should have had it in to begin with), but the screen updating is already being handled in the main macro; this is just one of about 30 sub-macros.

Thanks for the fix.

John

[JapanDave]

Yes it seems that those cells with #VALUE! are the culprits. Have they been there before?

[snb]

You could consider using Excel's builtin facilities

Please Login or Register  to view this content.

[jomili]

Looks like my initial problem was a red herring. The problem IS the #VALUE! errors. These recently appeared, because I changed this piece of code

Please Login or Register  to view this content.

for this piece of code:

Please Login or Register  to view this content.

(see the post at http://www.excelforum.com/excel-prog...a-values.html; I THOUGHT this was solved. Basically all I wanted to do was to fill the blanks in column X with values from column D)

[JapanDave]

Glad that things are sorted out now.

[jomili]

Me too. BTW, looks like the link I posted was bad, so here it is again: http://www.excelforum.com/excel-prog...la-values.html

For right now I'm going back to my old method, but if anyone wants to help me get the evaluate method to work without producing Value errors I'd appreciate it.

[snb]

But what about this ?

[jomili]

SNB,

The link you posted takes me right back to here.

[JapanDave]

Have you tried Snb's code to see if the same error occurs? I think that is why he has linked you to that post.

[jomili]

Thanks JapanDave. No, I hadn't tried SNB's code, because it was a solution to a problem that's not really a problem. My original code was failing due to Value errors in the data. I thought the problem was with the code that was failing, but my real problem was with the code that was producing the Value errors. Now that I've resolved THAT problem, I'll try SNBs code as a substitute for my original code and see if I notice any benefit. SNB's code is certainly more compact.