P
Paul Mac
HI All
I'm having some interesting issues with a workbook, that when a particular users updates the file, it is causing some sort of corruption in the open sequence of the file. Normally the file takes 2 - 3 seconds to open, as there are some dependant routines that are part of out Document Management System. Locally it opens in under a second. When the file has the problem it takes over 20-30 Seconds and the CPU is flatlined for that whole time
I have worked out how to overcome the problem by
1. Exporting & Removing all Forms and Module
2. Removing the worksheets & saving to a new locatio
3. Saving the empty file (with a single blank worksheet), re-opening, and saving again
4. Re-importing all of the exported components again
This then works, and until the user / computer in question opens and saves the file, it is all OK. But once they have used it, it reverts to the SLOOOOW version
The event which appears to be having the problem is during the load sequence (but before the Workbook_Open event)
Is there any way to enter a debugging mode to see what is happening at that moment. All of the cell ranges are very clean (without any straggling cells) and the scroll area is set on each open according to the used range, so the sheet doesn't have a large area
Any ideas on this one would be great
Specs: XL XP SP
Windows X
P4 1.7Gh
256MBRa
12.6Gb free on
I'm having some interesting issues with a workbook, that when a particular users updates the file, it is causing some sort of corruption in the open sequence of the file. Normally the file takes 2 - 3 seconds to open, as there are some dependant routines that are part of out Document Management System. Locally it opens in under a second. When the file has the problem it takes over 20-30 Seconds and the CPU is flatlined for that whole time
I have worked out how to overcome the problem by
1. Exporting & Removing all Forms and Module
2. Removing the worksheets & saving to a new locatio
3. Saving the empty file (with a single blank worksheet), re-opening, and saving again
4. Re-importing all of the exported components again
This then works, and until the user / computer in question opens and saves the file, it is all OK. But once they have used it, it reverts to the SLOOOOW version
The event which appears to be having the problem is during the load sequence (but before the Workbook_Open event)
Is there any way to enter a debugging mode to see what is happening at that moment. All of the cell ranges are very clean (without any straggling cells) and the scroll area is set on each open according to the used range, so the sheet doesn't have a large area
Any ideas on this one would be great
Specs: XL XP SP
Windows X
P4 1.7Gh
256MBRa
12.6Gb free on