Bob,

There is a significant difference though between an enum object and .h files. The .h files are read at compile time, i.e. when the class is saved or when you compile classlib. So the executing code at runtime only sees a constant the compiler put there. An enum object would have property values set/read at runtime from potentially #define constants.

>I like the naming convention suggestion. Chaining the #includes together is where I thought I'd have to go.
>
>The only other thought I had was to create an enum class for each classlib. I could put it into the base class and all my sub-classes would see it. A little more awkward to reference things as THIS.enum.BADINPUT instead of BADINPUT though. Plus its a pain to see the whole collection of values compared to viewing a .h file.