Mismatch error 13 out of the blue

[BlondOIverBlue]

This macro I use to auto-create a report from raw data works fine for a while, but then, like today, for no reason that I can see, I get a mismatch error. The debugger points to a certain point in the code and I used my previous solutions to attempt a fix, but no matter what I do, the macro tanks.

I have attached a sample copy of the raw data I use the macro on (macro is enabled/loaded already). It has to be something silly I'm overlooking. Any help is appreciated.

[TMS]

The code is crashing in this section on the line highlighted:

Please Login or Register  to view this content.

At the crash point, i=9, and:

Please Login or Register  to view this content.

So, you're trying to extract TimeValue("Start Time") which is why you get the Error 13 Type Mismatch

I don't really follow the logic of the code (it's early and I'm not fully awake) but that's where it's at.

Regards

[BlondOIverBlue]

Hrmmm....ok, I think I see what you mean, but I'm still a little puzzled why all week it worked flawlessly and tonight, this. I looked at that portion of the code and all "seems" to be in order.

[TMS]

I'm guessing it's because there's only one line of data at that point so the end(xlup) isn't giving you a block of data to make comparions with.

If, for example, you had a second line of data and you started from row 10, you'd be selecting $L$6:$M$7. Maybe this is the first time you only have one row of data?


Note that you can do this:

Please Login or Register  to view this content.

to convert the text numbers to real numbers instead of looping throgh the rows.

Regards

[BlondOIverBlue]

Note that you can do this:

Please Login or Register  to view this content.

to convert the text numbers to real numbers instead of looping through the rows.

Maybe I'm just not in the state of mind to look at code given it's two o'clock in the morning, but, while I get the gist of what you said, for some reason, I'm having issues using this code and testing it. I keep getting a compile error.

[Andy Pope]

As TMShucks pointed out the error occurs when there is a single Tech ID row. The use of .End(xlUp) causes the returned range to include non valid data.
This additional code will check for single row items.

Please Login or Register  to view this content.

[BlondOIverBlue]

After I got some sleep, I took another stab at this. Once I saw Andy Pope's reply, it all made more sense!

When the error happened before, I just chalked it up as "not solvable" because I assumed that the raw output data I get from my database was the cause due to the intermittent nature of the error. I never thought it was the macro itself per sé. I can't believe for the last year I overlooked that. Thanks so much everyone!