Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Processing Overhead during Cut/Insert
I have some code that I would like to optimise because it can run
quite slowly; In a procedure that involves numerous Cut & Insert operations is there a greater processing overhead if one references the EntireRow as opposed to a Range. I would be grateful for any comments Kind Regards Phil |
#2
Posted to microsoft.public.excel.programming
|
|||
|
|||
Processing Overhead during Cut/Insert
you can try to copy and destination then clearcontents instead of cut and paste for example Sub test() Range("a1:a10").Copy Destination:=Range("b1:b10") Range("a1:a10").ClearContents End Sub Post your code may be there is something else slowing it. Cesar Zapata Phil Kenchatt wrote: I have some code that I would like to optimise because it can run quite slowly; In a procedure that involves numerous Cut & Insert operations is there a greater processing overhead if one references the EntireRow as opposed to a Range. I would be grateful for any comments Kind Regards Phil |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
Processing Time | Excel Worksheet Functions | |||
Processing Data | Excel Worksheet Functions | |||
Data Processing | Excel Programming | |||
Data Processing | Excel Programming | |||
SaveSetting/GetSetting: not high-overhead? | Excel Programming |