Michael,

Been there...

Appreciate your appreciation...

Will you be gone for the weekend????

--
steveB

Remove "AYN" from email to respond
"MichaelC" wrote in message
...
Thanks, Steve - for teaching me how to fish rather than giving me one.
Although I've heard some ladies say that if you teach a man how to fish
rather than giving him one, you get rid of him for the rest of the
weekend!

"STEVE BELL" wrote:

Make sure that
Option Explicit
is at the top of your module.

Use the Debug menu
select - Compile Project
(you can also add a toolbar button to do this)

Each time you compile Excel will high light an offending line of code.
Try to fix the line.
Continue this until the code is clean.

--
steveB

Remove "AYN" from email to respond
"MichaelC" wrote in message
...
The runtime error appeared the first time I ran the Sub, and when I hit
Debug, it highlighted, in yellow, the offending line of code.
I fixed what I thought was wrong and ran the Sub again.
The runtime error reappeared but highlighting a different line of code.
This has gone on all morning - with sometimes different, sometimes the
same
line of code.
So I can't even pinpoint exactly which line is in error.
Perhaps the error is apparent to an experienced eye such as yours.

"Sarah B via OfficeKB.com" wrote:

Michael,

What do you mean when you say that it crops up on most of the line?
I'm
assuming you've done something like putting breakpoints on lines,
commenting
out other lines, etc?

Sarah