S
spunkymuffmonkey
Hi all,
I have a some code that I am using to read the contents of each cell of the
multiple rows in a 4 columned table.
I am experiencing a slow down when my code gets to a particular line of code
with is:
Set myRange = oTable.Rows(i).Cells(j).Range
when the table contains less than 100 rows the macro flies along really
quickly, however when the number of rows is increased to 500 or so, my code
grinds to a snail's pace, but strangely (at least in my eyes) this slowdown
occurs on the very first line in the table.row.count is high (I would've
thought that the code would start struggling after executing a few times.
Could anybody shed any light on this, and also point me in the direction of
some information surrounding the memory utilisation of vba as I am creating
more and more complex coding without any understanding of the implications of
my designs.
Many thanks for looking.
I have a some code that I am using to read the contents of each cell of the
multiple rows in a 4 columned table.
I am experiencing a slow down when my code gets to a particular line of code
with is:
Set myRange = oTable.Rows(i).Cells(j).Range
when the table contains less than 100 rows the macro flies along really
quickly, however when the number of rows is increased to 500 or so, my code
grinds to a snail's pace, but strangely (at least in my eyes) this slowdown
occurs on the very first line in the table.row.count is high (I would've
thought that the code would start struggling after executing a few times.
Could anybody shed any light on this, and also point me in the direction of
some information surrounding the memory utilisation of vba as I am creating
more and more complex coding without any understanding of the implications of
my designs.
Many thanks for looking.