![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, I am using a form to enter data to a table. I have used the wizard to create the combo box using another table as a source of options to enter text values. The source table and destination tables both have the appropriate fields set as text. However when I use the form and check the table it is not the text value that is there but a corresponding number that is the primary key for that table. Any ideas anyone? Thanks, Will |
#3
| |||
| |||
|
|
My guess is that you used a for one of the "text" values. Even though you may see text in datasheet view, those store an "index value" into a list, and they rise up to bite you in the tender places. If that is the case, get rid of that Field Type, handle it a different way, and, voila', you will not face this problem any more... you may face other problems, of course, but you'll have removed a potential source of problems. (IMNSHO, Lookup Fields are only helpful to novice end-users who use their data directly from the datasheet; for more advanced users and developers, they are just a source of irritation.) In such cases, I use a lookup Table, and _knowingly_ store the recordID for the value... and, when I want the text, I use a Query that joins the two tables. Larry Linson Microsoft Office Access MVP "Will" <willcull (AT) yahoo (DOT) com> wrote in message news:d57ac5c5-1204-4847-8684-2f6a6fc0358a (AT) d62g2000hsf (DOT) googlegroups.com... Hi, I am using a form to enter data to a table. I have used the wizard to create the combo box using another table as a source of options to enter text values. The source table and destination tables both have the appropriate fields set as text. However when I use the form and check the table it is not the text value that is there but a corresponding number that is the primary key for that table. Any ideas anyone? Thanks, Will |
#4
| |||
| |||
|
|
Oops. *First sentence should read... 'My guess is that you used a Lookup Field for one of the "text" values.' *Larry "Larry Linson" <boun... (AT) localhost (DOT) not> wrote in message news:E7Yzj.11198$1_.4041 (AT) trnddc02 (DOT) .. My guess is that you used a for one of the "text" values. Even though you may see text in datasheet view, those store an "index value" into a list, and they rise up to bite you in the tender places. *If that is the case, get rid of that Field Type, handle it a different way, and, voila', you will not face this problem any more... you may face other problems, of course, but you'll have removed a potential source of problems. (IMNSHO, Lookup Fields are only helpful to novice end-users who use their data directly from the datasheet; for more advanced users and developers, they are just a source of irritation.) In such cases, I use a lookup Table, and _knowingly_ store the recordID for the value... and, when I want the text, I use a Query that joins the two tables. Larry Linson Microsoft Office Access MVP "Will" <willc... (AT) yahoo (DOT) com> wrote in message news:d57ac5c5-1204-4847-8684-2f6a6fc0358a (AT) d62g2000hsf (DOT) googlegroups.com... Hi, I am using a form to enter data to a table. *I have used the wizard to create the combo box using another table as a source of options to enter text values. *The source table and destination tables both have the appropriate fields set as text. *However when I use the form and check the table it is not the text value that is there but a corresponding number that is the primary key for that table. Any ideas anyone? Thanks, Will- Hide quoted text - - Show quoted text - |
![]() |
| Thread Tools | |
| Display Modes | |
| |