By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,264 Members | 1,100 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,264 IT Pros & Developers. It's quick & easy.

Combo box pain

P: n/a
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
Mar 6 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
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" <wi******@yahoo.comwrote in message
news:d5**********************************@d62g2000 hsf.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

Mar 6 '08 #2

P: n/a
Oops. First sentence should read... 'My guess is that you used a Lookup
Field for one of the "text" values.'

Larry

"Larry Linson" <bo*****@localhost.notwrote in message
news:E7Yzj.11198$1_.4041@trnddc02...
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" <wi******@yahoo.comwrote in message
news:d5**********************************@d62g2000 hsf.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


Mar 6 '08 #3

P: n/a
On Mar 6, 8:10*pm, "Larry Linson" <boun...@localhost.notwrote:
Oops. *First sentence should read... 'My guess is that you used a Lookup
Field for one of the "text" values.'

*Larry

"Larry Linson" <boun...@localhost.notwrote in message

news:E7Yzj.11198$1_.4041@trnddc02...
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...@yahoo.comwrote in message
news:d5**********************************@d62g2000 hsf.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 -
I'm not sure what I did as the wizard is pretty straightforward,
however copying a combox I entered directly into the form and making
the appropriate alterations did the trick. Thanks Larry
Mar 7 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.