Phucon-
The normal design is to use a code number in the main table that links to
the Primary Key of a lookup table that may also contain a description. When
the user want's to see the text instead of the code number, give them a
query that links the two tables and displays the related text from the
lookup table. The general reasoning is a number is more efficient to store
that text, but only marginally so. If the user wants text in the table, be
sure to give them a text field instead of a numeric field. You also don't
need the number as a Primary Key in the lookup table - just make the text
field the Primary Key.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)
-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of saigonf7q5
Sent: Wednesday, July 31, 2013 5:22 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Combox bound column
If the rowsource of a combo box has an id column and a description column,
and when we use the wizard to create a combo box, it bounds to the id column
automatically.
Each time an item's selected, it stored the id in the table instead of the
text (description). The users prefer to see the text in the table rather
than an id. I satisfied user's request by changing the bound column from the
id column to the description column.
My question is, should the bound column always be the id column? Or it does
not matter?
Thank you
Phucon
------------------------------------
Yahoo! Groups Links
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (2) |
Tidak ada komentar:
Posting Komentar