je napisao u poruci interesnoj
roups.com...
Changed to the recommended here.
,
The intended purpose of this was to have it jump to the next row
instead of cycling down one by one. The sample data is all for one
person but the actual data may have 1,000 rows between the same ID. I
had it reset to B1 each time the row changed to ensure all the IDs
were checked starting from the beginning. Sorry if it's a bit of a
mess. Learning as I go and have learned a great from other samples
posted by everyone and trying to piece this one together myself.

learning is ok, nobody born learnt.

but in this case, i see no puprose, just cpu wasting, because on next prog
lines you *explicitly* address ranges with range("B" & j) and similar, so no
"activate" make any sense, just slow down.

if you want to use built in find/activate features, you need to examine
*active* cell [retrieve its range] after doing find, and not to use flat
for/next

any speed improvement so far?

sometimes it is all due to the data structure/design matter. if badly
organized data, it is hard to have lightspeed program.

keep us informed.