How does it work? Why does it work this way?

[Merrion]

Is there any setting (e.g.

Option Even Stricter

) that prevents passing an integer through a parameter that expects an enum?

Or - what do you recommend instead?

[Atheist]

Is there any setting (e.g.

Option Even Stricter

) that prevents passing an integer through a parameter that expects an enum?

Or - what do you recommend instead?

But arent enums just fancy names for integers?

[Phill64]

But arent enums just fancy names for integers?

Yes, Integers, Longs or Bytes can be an enum.
The enum name itself is just an alias to a value of any of those types.

Being able to put a direct value in makes sense.
And why wouldn't you want to do so? especially in circumstances when you're reading settings or the like.

[Merrion]

No - enums should allow for a greater deal of type safety than integers.

If you have an enum

Public Enum VehicleDrivenWheels
    TwoWheelDrive = 2
    FourWheelDrive = 4
End Enum

you should not be able to say:

Dim MyCarDrivenWheels As VehicleDrivenWheels = 739

It is this way because when you combine enums (that are set as <flags()> ) together and this would technically allow any integer - but I'd like some way of saying : treat this enum as not combineable...even as a specific attribute you have to set to make it so...