object variable question

[Wedge120]

I am using the following code. It looks at a cell's value, then changes the color of another cell on the same row based on that value:

Please Login or Register  to view this content.

I used the object variable "cell" simply because it makes sense. But I realize I could have used "ce" or any something else because it is simply a variable taking on the properties of an object.

What I don't understand is how does the expression know which object I am referring to? Another example would be

Please Login or Register  to view this content.

I just don't understand how the code understands which object I am referring to. It seems as if the object is implied by context. But I am new to this and trying to make sense of it.

[royUK]

You should declare your variables
eg

Please Login or Register  to view this content.

[Wedge120]

You should declare your variables
eg

Please Login or Register  to view this content.

Based on what I have read, I agree, because it makes sense and can speed up the code (but I don't have experience in coding, so I am going by what I have read). But that still doesn't really tell me how the expression knows which object it points to.

Not trying to be nit-picky because I appreciate the help, but I really want to know.

[royUK]

Your code is simply looping through the objects, by declaring the variables correctly excel knows that it is looking for a Range object or a WorkSheet. See this

[shg]

What I don't understand is how does the expression know which object I am referring to?

You are iterating through a collection, in this case a Range.

If you don't declare cell (or whatever you call it; it doesn't matter, but for the fact that you should adopt a variable naming convention and stick to it) as a Range, then you are iterating through the default collection of a range, which is Cells. To make it explicit (and you should),

Please Login or Register  to view this content.

An range has other collections, including Rows and Columns.

See Help for Returning an Object from a Collection

[Wedge120]

You are iterating through a collection, in this case a Range.

If you don't declare cell (or whatever you call it; it doesn't matter, but for the fact that you should adopt a variable naming convention and stick to it) as a Range, then you are iterating through the default collection of a range, which is Cells.

I think that's what I was wanting to know.

To make it explicit (and you should),

Please Login or Register  to view this content.

An range has other collections, including Rows and Columns.

See Help for Returning an Object from a Collection

Much appreciated.

[snb]

In this case I don't think specifying or declaring serves any purpose:
You can't declare better than the VBA-compiler can, so leave the 'thinking' to computer.
See:

Please Login or Register  to view this content.

[royUK]

One of the greatest Excel Guru's opinion

[shg]

In this case I don't think specifying or declaring serves any purpose:
You can't declare better than the VBA-compiler can, so leave the 'thinking' to computer.

I'll go on record saying that is a lousy suggestion shared by vanishingly few competent programmers.

And all those typenames uninformatively return "Range"

[snb]

And all those typenames uninformatively return "Range"

What is so uninformative about the dimension those variables have ? (what declaring is all about)
Do you suggest this is possible ?

Please Login or Register  to view this content.

I think your comment underlines my proposition you can't do better than the VBA-compiler.

[royUK]

If Variables aren't declared explicitly then Excel assigns them as a Variant. This can cause longer processing times.

If Variables aren't declared properly & Option Explicit used then typos will lead to unwanted variables being created, & possible make later code not run as expected.

Declaring Variables properly makes for faster code & easier maintenance

[snb]

Please Login or Register  to view this content.

Quod non, as I showed you with

Please Login or Register  to view this content.

[shg]

Quod non ...

But it is. Look in the Locals window to see that it is a variant/object/range

[romperstomper]

In this case I don't think specifying or declaring serves any purpose

Since you've previously stated that you think declaring variables serves no purpose, why do you say "in this case"?