fpd833,
Thanks for your contribution, and I'll pass along a "STAR" for your example. I too am still learning VBA (as we all are - there are so many aspects to learn), so I appreciate your example.
Your example also worked fine for me during my initial testing. However, I just had to test out your example "further", to see what implications there are for a LARGER application.
I therefore entered data into the "lower reaches" of Excel's rows - around 65,000. And, guess what. I waited for 37 minutes and finally "gave up".
Now for my contribution... Because my background is heavily weighted on the Excel "functionality side", I've been exploring the "database functionality" fairly deeply.
I had previously written a VBA routine for another Tek-Tips posting, whereby the routine utilized this "database functionality". When I double-checked this example file, I found that I had populated the "database" down to row 65,535. The routine extracts rows containing data to the next sheet.
And guess how long it took ......exactly 2 seconds - Yes "2 seconds" (not the 37++ minutes).
My point is that, while "straight VBA" is quite useful in many situations, one should NOT overlook the "pure power" of the "built-in" functionality of Excel.
If anyone would like a copy of this Extraction Example, please feel free to ask. Just email me, and I'll return the file via return email.
A final note: The example provides an additional option to check "specific columns" for being blank.
Regards, ...Dale Watson dwatson@bsi.gov.mb.ca