All-
When I type Worksheets("Sheet1") into the vba ide editor the intelisense shows "_Default(Index) as Object". My question for everyone is if worksheets are built-in objects then why can't you drill into built-in objects and get intelisense help.
For example, we all know the Range object exists off the worksheets object. However, if you type Worksheets("Sheet1"). and you would expect intelisense to popup with list objects off worksheets object so you can find range object. However, the ide does not do that.
The only way I have been working around this issue is dimming a variable as worksheet then doing the variablename. and the intelisense works like a charm. I am guessing that is because it is using early binding.
Can anyone tell me why the built-in objects do not work like local objects or is this behavior by design?
TIA,
msqrd1979
When I type Worksheets("Sheet1") into the vba ide editor the intelisense shows "_Default(Index) as Object". My question for everyone is if worksheets are built-in objects then why can't you drill into built-in objects and get intelisense help.
For example, we all know the Range object exists off the worksheets object. However, if you type Worksheets("Sheet1"). and you would expect intelisense to popup with list objects off worksheets object so you can find range object. However, the ide does not do that.
The only way I have been working around this issue is dimming a variable as worksheet then doing the variablename. and the intelisense works like a charm. I am guessing that is because it is using early binding.
Can anyone tell me why the built-in objects do not work like local objects or is this behavior by design?
TIA,
msqrd1979