Hi Matt.
Quick response before I leave.
I ran through the sample you'd provided, with F8, and have noticed something
interesting.
I have the borders set in my sample at every 4 rows.
I set the top border, drop four rows, and set my bottom border.
I then drop four more rows, and set my next bottom border.
I repeat this last item through to the end of my data field.

The code you provided will iterate through, and select the first 4 rows, and
merge-- exactly as desired.
It then iterates through the next four rows, and does nothing.
It then looks at the next row's border as a top border, interates through
the four, and merges them.
Essentially what I've found is that it merges 4, skips 4, merges 4, skips 4,
etc.....

Because this looks like a border issue, I clicked on format cells, and
checked to see if the bottom border from the previous cell-- above-- is
listed as a top border for my cell of interest, and it is.

This raises something that I'm curious about--
Does VBA code view the borders the same as the excel program does?

I.e., the bottom border for row 11 is technically the top border for row 12.
Does VBA view it as such?
If not, then is there code that would "force" the border at the bottom of
11, to be viewed as the top border of 12?


I hope this is clear.... if not, please let me know.
Good night.
And again-- thank you for your help.