I need explanation;

I wrongly assigned colUMN variable, then changed to colN But what is strange vba has started to act all Column method with colUMN.

When I use intellisense it is written as Column, but when I press enter it goes back to colUMN. Strangeness is taht it works as range.Column property fine. I think I have changed the property of vba unwillingly, will it be bad for my further code?

CodePudding user response：

The VB Project Editor tries its best to keep capitalization consistent on each variable name that you type, but it does occasionally mess up. But its just that, capitalization, it doesn't actually mess up the code. Although it might be written colUMN, the Range object still only has a property called Column and when the code runs, it will properly give its Column value.