Hi: I use Excel automation in two Visual Basic Applications to create reports as Excel workbooks. The problem is that on some machines, it can be very slow to generate these workbooks. I am running Windows 2K Pro and Office 2000, and I have never noticed this problem myself as the developer. However different users who use different Windows/Office configurations report that there is a long delay at times when generating these reports. It seems that usually they are slow to generate on Windows XP. It seems as if there is a very long delay at the first in loading Excel before the report even starts to generate. I have spent a great deal of time researching on this trying to find a solution. I have used all of the "optimization techniques" in my code that people have suggested, but this has not helped. I do not know what is happening, but it appears that the major slow down may occur when changing the margins or page orientation when certain printers are the default printer. I really need to find out why it is fast usually in Windows 2000 but slow in Windows XP. I can provide any further information anyone requires to find a solution. Please help! My e-mail is Brian149@cox.net. Thanks in advance.

Was the code written, or recorded? Only if it was recorded, then any 'print setup' stuff you do can explode to thousands of unneccessary lines of coee. Say these were recorded by 2000, then XP may need to do further translation on them to make its own sense of them. Other things to check include calculations being on or off. This can make a whizzy macro die on some machines. If you aren't sure, and if they aren't neccessary, then have your macro turn them off (and back on at the end if need be). Tom

I am not sure what you mean by "recorded". My VB applications are creating the workbooks "on the fly". No templates are being used. I do very few calculations at all in these reports. At most I do a summation of the values in a column. So I would not think that changing the calculation value would cause the kind of slow down we are seeing on some workstations. I have tested this before and it has seemed to make no difference. I will add it to my code because I am desparate to find a solution, but I do not think this is it.