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

A waste

--
Don Guillett
SalesAid Software
(E-Mail Removed)
<(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> 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
>

Thanks Don,

Yep! I figured that - But - I was concerned that I may be missing something.

"Don Guillett" <(E-Mail Removed)> wrote:

>
>A waste