Excel 2003 failing on big macros

  • Thread starter Thread starter Pete
  • Start date Start date
P

Pete

I am crunching over 40,000 rows of data and have used
macros successfully in Excel 2000 to automate the
process, and just upgraded to Excel 2003 and the same
kind of macros are blowing up, even though the functions
employed work fine when I build the new macros. At
around row 42,000 they just stop copying down, even
though I am nowhere near the bottom row (62,556). Also
they run ten times slower than the Excel 2000 on my older
machine, even though the new machine has 5x the RAM and
ROM of the old machine.

Is there some new security setting that I could reset
that may be causing this blow up?

Thanks.
Pete
 
Pete wrote
I am crunching over 40,000 rows of data and have used
macros successfully in Excel 2000 to automate the
process, and just upgraded to Excel 2003 and the same
kind of macros are blowing up, even though the functions
employed work fine when I build the new macros. At
around row 42,000 they just stop copying down, even
though I am nowhere near the bottom row (62,556). Also
they run ten times slower than the Excel 2000 on my older
machine, even though the new machine has 5x the RAM and
ROM of the old machine.

Is there some new security setting that I could reset
that may be causing this blow up?
Click to expand...

Pete,

I am not aware of any special settings or triggers.

You might try to identify where your VBA is breaking down.

You can follow the procedure outlined here: http://tinyurl.com/5ann7 to
assist you in identifying where the code dies.

Perhaps once you have found the troublespot, you can rewrite it in a
different fashion to solve your problem.

In any event, it would be helpful to learn where the code breaks down.

Hope this helps.

Regards,
Kevin
 
Thanks Kevin--as I recall, it does not post an error.
Instead, it stops copying blocks of cells down, and the
cursor just skoots a few columns to the left and stops
there.

I'll try running it again after the holiday weekend and
will look at the macro itself to try to sort it out as
you suggested.

Regards,
Peter
-----Original Message-----
Pete wrote

Pete,

I am not aware of any special settings or triggers.

You might try to identify where your VBA is breaking down.

You can follow the procedure outlined here:
Click to expand...
http://tinyurl.com/5ann7 to
 
Pete wrote...
Thanks Kevin--as I recall, it does not post an error.
Instead, it stops copying blocks of cells down, and the
cursor just skoots a few columns to the left and stops
there.

I'll try running it again after the holiday weekend and
will look at the macro itself to try to sort it out as
you suggested.

Regards,
Peter
Click to expand...

Hi Pete,

Even if it does not post an error, by using the LogIt routine, you can
identify where the macro stopped. That ought to be helpful.

Good luck. Let us know how you make out.

Regards,
Kevin
 
Back
Top