'Capitalized letters in method name after wrongly assigning colUMN variable
I wrongly assigned colUMN variable, then changed to colN but 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.
It works as range.Column property fine.
I think I changed the property of VBA unwittingly. Will it be bad for my further code?
Solution 1:[1]
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.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Toddleson |