BreakPoint
Custom Control
This question really belongs in the LabVIEW forum ...
but, I'll provide a reply here since I'm already here. 
Place the information in the description for the enum. To enter linefeeds in the description box use Shift-Enter.
Then, you just need to do this:
Be sure to make the enum a typedef, but I think you said you already had that.
Obviously, if you're already using the description for documentation like a good little programmer, you can always chop out what you need from it.
Could you use Tags, as described by Darren here ?
You could place the information you need into a set of tags that are applied to your type def. The tags could be identified by a string representation of the enum index (such as "01", "02" etc.), and the actual value could then contain "8848m" and "8861m", then all you have to do is format your enum index into a suitable tag identifier and extract the info.
Because the Tag info is embedded within the object, it will always remain. What I haven't tested here is creating a type-def from the enum, and then checking new controls based on that type-def for user tag info. The tag info may get stripped out?
Attached is my idea in LV 8.6
Update: Tried creating a type-def from the enum with the tags in, and the new control also had the tag info! So all new controls that are associated with the type-def get the tag info as well. Now to test changing the tag info to see if the associated controls update too...
A quick follow up: there's a weakness. I cannot see a way to edit the tags of the type-def control 
Therefore, once you've created your custom control from a standard control, the embedded tags cannot be changed. The User Tags functions only allow us to change the tags of either controls (by reference) or vis (by reference). A type-def is a .ctl file, and this does seem to report back those tags associated within the control inside it. Therefore presumably one cannot change them.
Maybe Darren can throw a little wisdom on all this?
A typedef control is treated as a VI. I can't check this at the moment, but you can open a reference to it using the Open VI Reference primitive and then try to use that reference to modify the tags.
I'm guessing you will need to use the FP.Control[] property to get the actual control, but I didn't try this recently.
Yes, you are correct. I've just tried this, and by accessing FP.Control[0] I can get a reference to the type-def enum and change it's user tag details programmatically! 
The downside is, programmatic changes don't get flagged up in the type-def as changes, so they are not propagated down to any associated vi controls. To force this I had to make a simple cosmetic change (I moved it a couple of pixels), which enabled the "File>Apply Changes" menu item. Doing this on a Strict Type Def works brilliantly, but user tag changes are not propagated back for ordinary type defs 
So, craigc, to use user tags one would need to force the type def into a strict form and also be prepared to programmatically make the modifications as user tags can't be edited through the ordinary "properties" window, unlike smercurio's Description text suggestion - which sounds a lot easier
Would it be acceptable to use a ring instead of an enum ? This type allows to set non sequential values. This may be a solution if, like in your example, the values are integers.
