Neither one is that difficult once you know the Object Model. And lack of
knowledge has never stopped me from wanting a more robust/efficient
solution. ;)

--
Regards,
Zack Barresse, aka firefytr
To email, remove NOSPAM


"Luke Alcatel" wrote in message
...
Fair enough. I did it with loops because 1) I'm a programmer rather than
an
Excel expert and I've never heard of AutoFilter. I do a little VBA
programming when I have to, 2) After reading your mail I looked at
AutoFilter in VBA help. I have a feeling that at his knowledge level
David
would be much better off studying and understanding my loop as opposed to
getting into the esoterica of filter object manipulation.

Luke

"Zack Barresse" wrote in message
...
The reason I ask exactly what you're doing is that if you are looking for
blank rows, you don't need a loop, we can use AutoFilter, which is (in
most
cases) faster than looping. If we can avoid loops, it's generally best.

--
Regards,
Zack Barresse, aka firefytr
To email, remove NOSPAM


"Luke Alcatel" wrote in message
...
I don't understand how an operation you perform on the worksheet after
you
import data can affect the imported data but that might be my problem.

Seems to me that you don't want to hard code row 175 as an upper bound
but
instead preface your code with a little loop that searches for the
first
fully blank row that follows your poplulated rows. Does that sound OK
or
do
you still need to know how to write such a loop?

Luke

"Dave" wrote in message
...
Hi
I have a macro that clears the contents of a sheet after I have
imported the data into a database.
This works fine but if the data is less then 175 rows it leaves
blank rows in the database.
How can I get round this.
Not very good with VBA would appreciate any help
Macro as below:-

Range("A2:N175").select
Selection.ClearContents
Range("A2").Select
Workbooks("MyBook1.xls").Close SaveChange:=True