Hello. Another speed query from me. I've attached an example of the code.
If I have this exact code, in it's own module, in a workbook I'm in the process of building, with 40 sheets & it will be 27 modules, (there's only 6 for now) it takes 2.5 seconds to run. This piece of code will have to be run through for each day entered, 40 times per sheet. That'll be an eternity. If I have this exact code in a new workbook, it runs in virtually zero time. A message box with the time appears when completed. It's not all the code that will be running, it's the bottleneck.
Is it the number of worksheets causing the problem? Or is it a corrupted workbook? Is there a setting somewhere in excel that can be fiddled with? I've tried workbook open & repair without success. I'm asking the question because I'm trying to avoid starting again with a new workbook.
Thanks
If I have this exact code, in it's own module, in a workbook I'm in the process of building, with 40 sheets & it will be 27 modules, (there's only 6 for now) it takes 2.5 seconds to run. This piece of code will have to be run through for each day entered, 40 times per sheet. That'll be an eternity. If I have this exact code in a new workbook, it runs in virtually zero time. A message box with the time appears when completed. It's not all the code that will be running, it's the bottleneck.
Is it the number of worksheets causing the problem? Or is it a corrupted workbook? Is there a setting somewhere in excel that can be fiddled with? I've tried workbook open & repair without success. I'm asking the question because I'm trying to avoid starting again with a new workbook.
Thanks