Why does intellisense "disappear" at times?

I am a rare user of VBA (once a year) for the past 8 years and always have de ja newbie experience. Because I don't recall the DOM very well I rely on intellisense. At times using certain kewords/methods intellisense gives me the impression Im doing something wrong because of its lack of response.

For example I use the Cells method because I am using dynamic single cell references.

Cells(r,c).interior.color =255

Intellisense will die whenever I use the cells method. Why is this?

I've stared using a work around for this intellisense case of A.D.D.

Range(Cells(y, x).Address).Interior.Color = 255

or I type garbage code and clean it up

Cells.Interior.Color=255

This will keep intellisense offering keywords to the DOM challenged. Am I coding in an incorrect fashion to confuse VB?

Compile your project and fix errors, then IntelliSense will return.

No errors. Same problem. Just type any code with the Cells property for yourself. This is one I did.

Private Sub Worksheet_SelectionChange(ByVal Target As Range)
r = Target.Row
c = Target.Column
Cells(r, c).Interior.Color = 255

End Sub

Intellisense dies after

Cells(r,c)

.[No intellisense]

Range(cells(r,c).address

.[You have intellisense]

How would you go about changing a cell attribute of a specific sell that you would not know until after runtime? Hardcoding is not an option. Its not a relative position from a clicked cell (i.e. target object and offset cant be used). Intellisense seems to die unless I do this.

As is often the case, the Item property of the Range does not have a specific return type, so intellisense has no information to work with.

Thanks. This issue was annoying me. I thought I was coding in some esoteric way.

Nope!
It's the same thing if you use ActiveSheet for example. Because it returns a generic Object type, you don't get intellisense.

99.885% of the time it is unnecessary to select or activate anything in code, and it is more efficient not to if possible.