wow. If a procedure is 4 pages then it strikes me that its way too big. IMHO
Try to break it down ito pieces if you can. Have you tried stepping through
it?
To do that, put a breakpoint in somehwre near the start (F9) and then step
(F8)

This might allow you to see what its doingto that last line.

"kmbarz" wrote:

I've inherited an Excel spreadsheet that has a complex data handling macro.
If it's run on Excel 2000/Windows 2000 it runs just fine. If I run it on
Excel 2003/Windows XP Pro, the data in the bottom line of each table it
creates corrupts.

I've isolated the issue down to one subroutine, but even that printed out is
four pages, and I'm new to the Excel model to boot. So, is there any
resource out there for what is likely to break in VBA in going from 2000 to
2003?

Thanks!