hi -
i have field in a table which is described as a number type. it uses a 2 column combo box to get its value. the first column has a code number and the second a verbal description. the first of the 2 columns is bound to the field and the column widths property looks something like this: ' 0";1" ' which you probably already know signals the intent to display only the text field (and not the number).
the people who use this want to add more fields to the look up table (combo box) and i have learned that the number field has no real meaning (i inherited this from someone who left before i came on the scene). so here's the question: i see no point in retaining the paradigm and would imagine it'd be a little slicker if i could somehow eliminate the reliance upon the number field. however, when i re-configure the field's properties in the table's design view and declare the field to be text (and not anh longer number), bind the 2nd (text column) to the field, what happens when i open the table and view the field is that i see it populated with numbers (which i don't want to happen), and the drop down list looks the same as before (which i would want).
i figured that the above would have gotten ms access 2000 'exchange' the numbers in the table's fields for the textual labels.
any ideas wrt how to accomplish that (the exchange) seamlessly w/o what would appear to be having to manually enter the text for every numerically coded value in each row?
i have field in a table which is described as a number type. it uses a 2 column combo box to get its value. the first column has a code number and the second a verbal description. the first of the 2 columns is bound to the field and the column widths property looks something like this: ' 0";1" ' which you probably already know signals the intent to display only the text field (and not the number).
the people who use this want to add more fields to the look up table (combo box) and i have learned that the number field has no real meaning (i inherited this from someone who left before i came on the scene). so here's the question: i see no point in retaining the paradigm and would imagine it'd be a little slicker if i could somehow eliminate the reliance upon the number field. however, when i re-configure the field's properties in the table's design view and declare the field to be text (and not anh longer number), bind the 2nd (text column) to the field, what happens when i open the table and view the field is that i see it populated with numbers (which i don't want to happen), and the drop down list looks the same as before (which i would want).
i figured that the above would have gotten ms access 2000 'exchange' the numbers in the table's fields for the textual labels.
any ideas wrt how to accomplish that (the exchange) seamlessly w/o what would appear to be having to manually enter the text for every numerically coded value in each row?
