right now i am using this:
Set rngfound = ws4.Columns("B:B").Find

just wondering, if it would be better to actually determine the exact range in
column B rather than searching the entire column. most of the rows are going to
be blank, anyway.


--


Gary

If there is a difference it is so small as to not be noticable. Find is smart
enough to only look in cells that have values. Oddly enough in most cases it
would probably be slower to define the range to search as the time taken to
define the range is probably longer than the extra work potentially done by
the find... I have not tested this against a sheet where the used range gets
messed up which as a guess would be the only place where find might be
inefficient...

In short leave your code as is (IMO)...
--
HTH...

Jim Thomlinson


"Gary Keramidas" wrote:

right now i am using this:
Set rngfound = ws4.Columns("B:B").Find

just wondering, if it would be better to actually determine the exact range in
column B rather than searching the entire column. most of the rows are going to
be blank, anyway.


--


Gary

ok, jim, thanks.

--


Gary


"Jim Thomlinson" wrote in message
...
If there is a difference it is so small as to not be noticable. Find is smart
enough to only look in cells that have values. Oddly enough in most cases it
would probably be slower to define the range to search as the time taken to
define the range is probably longer than the extra work potentially done by
the find... I have not tested this against a sheet where the used range gets
messed up which as a guess would be the only place where find might be
inefficient...

In short leave your code as is (IMO)...
--
HTH...

Jim Thomlinson


"Gary Keramidas" wrote:

right now i am using this:
Set rngfound = ws4.Columns("B:B").Find

just wondering, if it would be better to actually determine the exact range
in
column B rather than searching the entire column. most of the rows are going
to
be blank, anyway.


--


Gary