I have a single 23,000 lines of VBA code Excel application (with 28 sheets
with lots of data), which migrated from 2007 to 2010 without presenting any
unexpected behaviour except for these two solid and re-testable "appearance
problems":

1. The frequency of running into a condition like: (Not Responding) has
increased in frequency with a factor of 10-20. It is annoying to look at and
my product receives some heavy criticism. However, my code is performing
every job successfully and perhaps 5-10% faster than under 2007 Excel 12.0,
so all is mostly good, but it IS annoying to see all of these (Not
Responding) appearing so frequently,.... people lose faith in my code for no
other reason.

2. I have never ever under any previous Excel version had my screen and
forms going completely WHITE while (Not Responding) has happened a few times.
The screen will eventually display normally, when my VBA code has finished
its job. User forms go WHITE too, and return to normal display once my VBA
code completes.

I have disabled ALL add-ins and have tested my application on Office 2007
after initially migrating it to 2010, guess what, 2007 have none of the above
problems.

I am running on a dual core 2.1 GHz machine (4GB of memory) with Windows 7
quite up-to-date and I have no systems registry problems or performance
problems on my machine.

I wish that someone in the Excel development team could make a parameter
available to VBA programmers where we could adjust (just for our special
applications) the time Excel waits for VBA to complete its journey before
Excel issues (Not Responding). Some of us developers do not need the (Not
Responding) at all because we continually display the progress of our VBA
code to the user who should not be confused AT ALL with (Not Responding)
flickerings on the screen.

Can we please move forward on this problem please?

Regards,
Peter Sie.