I probably should add a little more detail to this.

What I need it to do is tell my processing code which format to use for which fields. I will send a request to a server which has specific field values. Depending on a condition, in this case which carrier/payor, it will use the appropriate information from that criteria to format the value being put into the message.

There are not a ton of fields that will have variable formats, maybe 10, so I think it's workable. Just trying to figure out the best table/form way to handle it.

>That looks rather complicated. I would say, take a hint from the way FoxPro stores dates: they are stored in a standard format (in this case, YYYYMMDD, in 8 bytes (not very efficient, but that is not the point)), but depending on some SET commands, the data are shown in different formats.
>
>I think that would require unbounded fields (no .ControlSource), and the data would have to be converted to and fro, on Form.Refresh() and on saving data.
>
>>I need to create a table and form that will allow choices in different formats for certain field values.
>>
>>For example:
>>
>>Social Security Number could be:
>>

>>999999999
>>999-99-9999
>>999 99 9999
>>

>>A date could be:
>>

>>YYYYMMDD
>>YYMMDD
>>MMDDYY
>>MMDDYYYY
>>

>>A full name could be:
>>

>>Last, First Mi
>>First Mi Last
>>Last First Mi
>>First Last
>>

>>What would be the best approach for this?