Ah, I see why you asked about using the underscore character. My lord...on my screen your post is MORE THAN two screen widths!

Here is that awful line properly underscored.
[vba]oRange.Typetext Text:="For those programs applying for" & _
"pancreas transplant, access to both the simultaneous " & _
"pancreas kidney (SPK) and pancreas (PAK/PTA) UNOS RFI " & _
"must be granted to the BQCT." [/vba]

Ack, the code is so hard to read that I am going to have to pull it out and look at it. Yikes.

The underscore is especially helpful in these cases of long strings. Use it in conjunction with the ampersand character (&). For each chunk of text make an ending quote, then a space, the ampersand, then a space, and then the underscore.

You MUST have each chunk of text (string) within quotes. Otherwise you get a parsing error.

Oh and if you have Intellisense turned on (which you do...don't you), then here is an oddity.

"blah blah"& _ (no space before &) will turn into "blah blah" & _ (with a space) automatically by Intellisense. It will NOT however make a space before the underscore. So "blah blah" &_ will NOT turn into "blah blah" & _ by Intellisense.

Why? Because back in the old days....ah, the old days...it was very common to use the underscore character in the names of things.

Sub Make_It_So()

Actually you still see this, but perhaps not as often. So Intellisense does not assume (good dog) that all underscores should have a space before them...which is true. But all ampersands (that are not being used as actual text that is) do.