Andrew.Kirkham@gmail.com wrote:
> Well obviously I can change the name in the enum from Tan to something
> else, but the point was that I shouldn't have to do this. Technically I
> haven't used the reserved word Tan, I have used ColourID.Tan. The VBA
> compiler incorrectly interprets this.
>
> Perhaps I'm just being a C programmer about it and expecting things to
> work as they should!

....more interestingly if you use a vba reserved enumerator name in a
new enumerator then it overwrites the existing one without any warning.

e.g.

Enum TRY
vbRed = 1
End Enum

Public Sub TEST()
MsgBox TRY.vbRed
'msgbox displays 1, as expected
MsgBox vbRed
'msgbox displays 1, not 255
End Sub

There are of course ways around this as Andrew says, but it is worrying
that there is no warning that this is happening. If you write a new
function with the same name as a user defined enumerator it complains,
if you write a function with the same name as a "hard-coded" one (e.g.
function vbGreen as integer) it doesn't. Very odd !