Definitely agree we need more example :-). To do what you're wanting, you would create three cards. You can see them if you open this up (using the status example you mentioned):
Rules
status+*right+*structure status+*right+*defaultPointer : open status+*right+*autoname
status+*right+*createInherit from left card status+*right+*readInherit from left card status+*right+*updateInherit from left card status+*right+*deleteInherit from left card status+*right+*captchayes
status+*right+*head{{:head|core}} status+*right+*layoutdecko org layout 2 status+*right+*styleDECKO ORG SKIN status+*right+*script16 items
status+*right+*help status+*right+*input typeradio status+*right+*guideEditing Guide This default guide will appear in the full... status+*right+*content options{"referred_to_by":"Ticket Status Options"} status+*right+*content option viewsmart_label
status+*right+*on create status+*right+*on update status+*right+*on delete
status+*right+*thanks status+*right+*follow fields*nests status+*right+*follow
status+*right+*default is a blank Pointer card, which makes new cards ending in +status be Pointer cards.
status+*right+*input being "select" makes it a dropdown rather than the standard Pointer interface.
status+*right+*options is a search that determines what will appear in the dropdown.
Note that you can also get to these from any card that ends with +status — just go to the Options tab and the settings subtab (see set and setting).
Once those cards are created, anywhere that |any name|+status is created it will be a pointer, and in that context and whenever it's edited you'll get a dropdown menu. The typical use would be to put in a type form (e.g., Ticket+*type+*structure).
--John Abbe.....Fri Mar 12 19:59:32 -0800 2010; updated May 2