If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Option Groups in a Table
Is there a way to use an Option Group in a table, instead of creating a form
with unbound forms and have to create code to insert the data in the table? |
#2
|
|||
|
|||
Option Groups in a Table
You can create lookup fields in tables but this is generally considered bad
since data entry should be done from forms, code, queries, and NOT tables. -- Duane Hookom MS Access MVP "Lisa" wrote in message ... Is there a way to use an Option Group in a table, instead of creating a form with unbound forms and have to create code to insert the data in the table? |
#3
|
|||
|
|||
Option Groups in a Table
Lisa
To add to Duane's observations, a lookup datatype field in a table means Access stores one thing (i.e., the key value), but displays another (i.e., the looked-up value). Unless you remember this, and everyone else who might use that table knows (and remembers), there'll be confusion and trouble. Regards Jeff Boyce Microsoft Office/Access MVP "Lisa" wrote in message ... Is there a way to use an Option Group in a table, instead of creating a form with unbound forms and have to create code to insert the data in the table? |
#4
|
|||
|
|||
Option Groups in a Table
On Thu, 20 Jul 2006 05:15:02 -0700, Lisa
wrote: Is there a way to use an Option Group in a table, instead of creating a form with unbound forms and have to create code to insert the data in the table? No. Why on earth not just use a bound form? John W. Vinson[MVP] |
#5
|
|||
|
|||
Option Groups in a Table
On Thu, 20 Jul 2006 08:16:41 -0700, "Jeff Boyce"
wrote: Lisa To add to Duane's observations, a lookup datatype field in a table means Access stores one thing (i.e., the key value), but displays another (i.e., the looked-up value). Unless you remember this, and everyone else who might use that table knows (and remembers), there'll be confusion and trouble. So the Lookup feature should NEVER be used at all? Suppose I have a table with a field named "Priority" that can have the valuesd "High", "Medium", and "Low". Should I create tblPriorities and put a link to the appropriate row in the field? -- Running MS Office 2000 Pro on Win2000 |
#6
|
|||
|
|||
Option Groups in a Table
I would create a small lookup table. I ALWAYS assume lists will change in
the future. -- Duane Hookom MS Access MVP "LurfysMa" wrote in message ... On Thu, 20 Jul 2006 08:16:41 -0700, "Jeff Boyce" wrote: Lisa To add to Duane's observations, a lookup datatype field in a table means Access stores one thing (i.e., the key value), but displays another (i.e., the looked-up value). Unless you remember this, and everyone else who might use that table knows (and remembers), there'll be confusion and trouble. So the Lookup feature should NEVER be used at all? Suppose I have a table with a field named "Priority" that can have the valuesd "High", "Medium", and "Low". Should I create tblPriorities and put a link to the appropriate row in the field? -- Running MS Office 2000 Pro on Win2000 |
#7
|
|||
|
|||
Option Groups in a Table
On Thu, 20 Jul 2006 12:20:31 -0700, LurfysMa
wrote: So the Lookup feature should NEVER be used at all? Suppose I have a table with a field named "Priority" that can have the valuesd "High", "Medium", and "Low". Should I create tblPriorities and put a link to the appropriate row in the field? If you're using the Lookup wizard, that is EXACTLY what Access is doing for you; it's then simply concealing the linking field from view, and creating a relationship to the Priorities table and concealing THAT from view as well... not to mention creating one or two probably redundant indexes. At least if you do it yourself, you know what's there! John W. Vinson[MVP] |
#8
|
|||
|
|||
Option Groups in a Table
"?Should?" If you want absolutes, ...
You'll find a lot of folks here in the tablesdbdesign newsgroup who recommend against using lookup datatypes in table definitions. As my response suggested, there are risks (confusion) with deciding to use lookup datatypes. Go ahead, if you're willing to do what you have to to mitigate the risk... (and I agree with Duane and John ... I find it easier to create a lookup table and make the connection explicit, and via forms. That way, I can always add new items to the list, and no one has to remember that what you see is NOT what you get.) Regards Jeff Boyce Microsoft Office/Access MVP "LurfysMa" wrote in message ... On Thu, 20 Jul 2006 08:16:41 -0700, "Jeff Boyce" wrote: Lisa To add to Duane's observations, a lookup datatype field in a table means Access stores one thing (i.e., the key value), but displays another (i.e., the looked-up value). Unless you remember this, and everyone else who might use that table knows (and remembers), there'll be confusion and trouble. So the Lookup feature should NEVER be used at all? Suppose I have a table with a field named "Priority" that can have the valuesd "High", "Medium", and "Low". Should I create tblPriorities and put a link to the appropriate row in the field? -- Running MS Office 2000 Pro on Win2000 |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Help again from Ken Snell (Query) | Randy | Running & Setting Up Queries | 22 | August 29th, 2005 08:15 PM |
Multiple Options Group | Patty Stoddard | Using Forms | 19 | August 4th, 2005 02:30 PM |
Table Design | A. Williams | Database Design | 3 | April 29th, 2005 07:02 PM |
Manual line break spaces on TOC or Table of tables | Eric | Page Layout | 9 | October 29th, 2004 04:42 PM |
Here's a shocker | Mike Labosh | General Discussion | 2 | October 26th, 2004 05:04 PM |