P
Poniente
Dear all,
I'm running vba code in multiple instances of Excel and I recently migrated from 2003 to 2010.
Something odd happens: processor load of _all_ processors occasionally falls well below 15% if any of the running instances uses the copy code with the format:
Range("A1:Z1").Copy Destionation:=Range("A2:Z4000")
Together with the fall in processor load, all instances of Excel temporarily freeze for a few seconds, even though the other instances are not executing this kind of code, and should keep running at near 100% processor load.
The code does not cause Excel to crash, but it does affect overall speed on every time this code is executed in any of the instances. Applications other than Excel are not affected.
To me it sounds like a bug in Excel 2010 (possibly 2007 as well) as the described problems were not happening when running multiple instances in Excel 2003.
This raises three questions for me:
a) Is there anyone out there that can confirm this problem?
And b) Is there a workaround?
For example:
1) Is there any other efficient way to copy a range without using the clipboard?
Or more specific:
2) Is it possible to copy to an instance specific (local) clipboard? (.. so nothing is ever accidentally copied between the multiple instances of Excel)
Thanks in advance for your efforts!
Poniente
I'm running vba code in multiple instances of Excel and I recently migrated from 2003 to 2010.
Something odd happens: processor load of _all_ processors occasionally falls well below 15% if any of the running instances uses the copy code with the format:
Range("A1:Z1").Copy Destionation:=Range("A2:Z4000")
Together with the fall in processor load, all instances of Excel temporarily freeze for a few seconds, even though the other instances are not executing this kind of code, and should keep running at near 100% processor load.
The code does not cause Excel to crash, but it does affect overall speed on every time this code is executed in any of the instances. Applications other than Excel are not affected.
To me it sounds like a bug in Excel 2010 (possibly 2007 as well) as the described problems were not happening when running multiple instances in Excel 2003.
This raises three questions for me:
a) Is there anyone out there that can confirm this problem?
And b) Is there a workaround?
For example:
1) Is there any other efficient way to copy a range without using the clipboard?
Or more specific:
2) Is it possible to copy to an instance specific (local) clipboard? (.. so nothing is ever accidentally copied between the multiple instances of Excel)
Thanks in advance for your efforts!
Poniente