to simplify this, say i have a table with a numeric field which we'll call numero. numero uses a combo box lookup table with two columns. one is a number field and the other is a text field. we'll call the fields in combo box numero_1 and text_1. numero_1 is the leftmost field and text_1 is to the right in the combo box lookup table. numero_1 is field that i've bound to the numeric field called numero in the access table.
when the user hits the drop down arrow (s)he sees a two column look-up list. on the left is the numeric column with numero_1's values and on the right is the text column with text_1's values.
and of course, numero_1's values are stored in the the numeric numero field in the ms access table.
i more or less inherited this way of doing this and what i would really like the user to do as (s)he enters this information is to store the value of text_1 column in another text based column which i'd gladly add to the ms access table.
if you've read this far, what is perhaps just as important to know is that the values of numero_1 have no intrinsic value! i didn't create this paradigm, and if i had all i would have done was create a combo box with the values of text_1 for the user to pick from. however......
the ms access table happens to have thousands of rows with values in the numero field --- so it's no mean task to manually convert each to its textual equivalent.
my gut tells me that ms access can be coaxed into handling the awesome conversion.
ideas are most welcome.
when the user hits the drop down arrow (s)he sees a two column look-up list. on the left is the numeric column with numero_1's values and on the right is the text column with text_1's values.
and of course, numero_1's values are stored in the the numeric numero field in the ms access table.
i more or less inherited this way of doing this and what i would really like the user to do as (s)he enters this information is to store the value of text_1 column in another text based column which i'd gladly add to the ms access table.
if you've read this far, what is perhaps just as important to know is that the values of numero_1 have no intrinsic value! i didn't create this paradigm, and if i had all i would have done was create a combo box with the values of text_1 for the user to pick from. however......
the ms access table happens to have thousands of rows with values in the numero field --- so it's no mean task to manually convert each to its textual equivalent.
my gut tells me that ms access can be coaxed into handling the awesome conversion.
ideas are most welcome.