I understand that it is best practice to never use Range.Select in
Excel VBA as it will often throw up bugs. I have found several examples
for this from trawling the groups and it has happened to me several
times when developing.

However, i am at a loss trying to understand where the problem lies.
Can anyone tell me what causes the bug?

If you need a specific example i can try and create one.

Many thanks

Dan

Hi Dan,

I'm working with Excel for many years now and I have never heard of
that problem / bug. In al my spreadsheest I use it, but never direct: I
use names in stead.

John.


--
jgmiddel
------------------------------------------------------------------------
jgmiddel's Profile: http://www.excelforum.com/member.php...o&userid=32714
View this thread: http://www.excelforum.com/showthread...hreadid=527197

I've never considered it a bug in excel--but I do consider it a bug in the code.

If you try to select a range that isn't on the activesheet, you'll get an
error. So you'll want to make sure you activate the correct workbook, then
select the correct sheet, then select the range (or use application.goto that
does this all at once).

Not a bug issue, but I've always found range.select followed by
selection.somethingoranother much more difficult to understand/maintain.

wrote:

I understand that it is best practice to never use Range.Select in
Excel VBA as it will often throw up bugs. I have found several examples
for this from trawling the groups and it has happened to me several
times when developing.

However, i am at a loss trying to understand where the problem lies.
Can anyone tell me what causes the bug?

If you need a specific example i can try and create one.

Many thanks

Dan

--

Dave Peterson

Many thanks for that, i think it was the activesheet issue you refer
to.