Use of filter vs. looping through cells

[Fedende]

I have a table with 2 columns, A contains either "Yes" or "No" while B contains other data.

I have a macro that takes all values where A = "Yes" and copies the rows to a different one.

Currently, I recorded the macro setting a filter by column a = "Yes" before copying the results.
Is it looping through column A, row by row, a more efficient option? I am wondering if this will require more resources from the pc (there can be 10 to 20 thousandth rows).

Thanks.

[FDibbins]

I would think that if you have a macro that 1st sets the filter to Yes, then copies what remains, to another location - and you have 10's of thousands of rows, that would be far quicker than having code loop through each entry and then copy 1 row at a time.

Doing the filter/copy/paste manually would probably take seconds - the macro for that would hardly take much longer

[FDibbins]

I would think that if you have a macro that 1st sets the filter to Yes, then copies what remains, to another location - and you have 10's of thousands of rows, that would be far quicker than having code loop through each entry and then copy 1 row at a time.

Doing the filter/copy/paste manually would probably take seconds - the macro for that would hardly take much longer

[Ed_Collins]

I strongly suggest you test both codes, and time the results. It's a lot of fun to compare the speed of two or more algorithms, both of which give the same end result, but do the task in different ways. You end up learning a LOT in the process.

25 years after learning about all of the many ways there are to SORT a list of items (bubble sort, heap sort, insertion sort, quick sort, merge sort, shell sort, library sort etc., etc.) I'm STILL fascinated by that subject!

[Fedende]

Indeed, I will try both options and find the one that works best.

Thank you!