Armysniper89
-
9/5/2011 11:16:33 PM
RE:Lookup Fields in Custom and System Tables
Well in most cases I have a field that would store the index into a table that contains the "State" in the United States a "job posting" is located in. That table has an integer called "StateID" and that is the index to the state. I might have another that contains Multiple index values being stored. For example, if I wanted to store all the states a user selects in a multi-select list box.
In my current site, any fields that lookup and store a single integer index, would be defined as an integery. Any fields that would store multiple index values...would be stored as text with mutiple indexes being stored as a comma separated list.
I am guessing that the first scenario of storing an integer for an index value like "State" and I am guessing I would do the same with a text value and use the drop down list. I had read before that it would store as a piped list. Just confirming.
Would be great for portability of records for the import toolkit, if you could specify a delimeter other than the "pipe".
|