B Butaambala Feb 3, 2005 #1 Does taking the time to set Application.CutCopyMode = False have a positive impact on procedure run-time? Thank you.
Does taking the time to set Application.CutCopyMode = False have a positive impact on procedure run-time? Thank you.
T Tom Ogilvy Feb 3, 2005 #2 Well, it removes the marquee (and the data from the clipboard), so that is positive if it isn't needed.
Well, it removes the marquee (and the data from the clipboard), so that is positive if it isn't needed.
B Bob Phillips Feb 3, 2005 #4 Can't believe that it does. I ran a few simple tests and there was very little difference, not scientific, but gives a fair indication. -- HTH RP (remove nothere from the email address if mailing direct)
Can't believe that it does. I ran a few simple tests and there was very little difference, not scientific, but gives a fair indication. -- HTH RP (remove nothere from the email address if mailing direct)
K keepITcool Feb 3, 2005 #5 I do have an issue with the OfficeClipboard.. (which afaik cannot be manipulated with VBA.) View/Taskpane in the caption of the taskpane select the clipboard from the dropdown click the options button... I definitely recommend DESELECTING "Collect without showing Office Clipboard" I havent thoroughly tested, but I've had some strange performance/memory problems in the past when this option was selected. -- keepITcool | www.XLsupport.com | keepITcool chello nl | amsterdam Tom Ogilvy wrote :
I do have an issue with the OfficeClipboard.. (which afaik cannot be manipulated with VBA.) View/Taskpane in the caption of the taskpane select the clipboard from the dropdown click the options button... I definitely recommend DESELECTING "Collect without showing Office Clipboard" I havent thoroughly tested, but I've had some strange performance/memory problems in the past when this option was selected. -- keepITcool | www.XLsupport.com | keepITcool chello nl | amsterdam Tom Ogilvy wrote :
