Originally Posted by
help_me_with_access
pretty simple, but there may be one hurdle. using excel objects in visual basic's environment and cycling through 3000 of them will probably crash the development environment completely. too much memory usage for sure.
so what you will want to do, what I do at least, is break the code every x iterations. what I usually do to stop vb from executing if i'm running a huge loop is put a message box popup based on iterations x / 1000 (or whatever increment results in the envrionment telling you "its not responding" for a period of time).
show a sample xl book. can you? do that, and you'll get some code back. deal?