Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
2007 (2003 compatability)
When data is being transferred to/from worksheets in the same wb, is it a best practice or a waste of time to actually issue wks1.activate then wks2.activate then wks1.activate, etc? The actual transfers are being accomplished using: wks1.activate <----- Is this smart or a waste? With wks1 .Range("A1").value = wks2.Range("A11").value .Range("A2").value = wks2.Range("A27").value .Range("A3").value = wks2.Range("A42").value .Range("A4").value = wks2.Range("A53").value .Range("A5").value = wks2.Range("A78").value End With TIA EagleOne |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Excel Data Protection Best Practice: AKA: Real Sheet Protection | Excel Discussion (Misc queries) | |||
help panel won't go away after saving a practice sheet | New Users to Excel | |||
Excel practice sheet. Can't view instructions. | Excel Discussion (Misc queries) | |||
search all sheets in book to find value and activate sheet with va | Excel Programming | |||
Transfer data from XL into Access: best practice | Excel Programming |