From: Lars Brownies on 17 May 2010 13:53 I know I shouldn't use lookupfields in tables. But does that also accounts for when you create a lookup in a field's table from a 'list of values'? For instance I want to create a lookup field for the field gender with values "M" and "F". Thanks, Lars
From: Arvin Meyer [MVP] on 17 May 2010 14:17 Do it in a value list in a combo box in your form. Users should NEVER see tables. -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.accessmvp.com http://www.mvps.org/access "Lars Brownies" <Lars(a)Browniew.com> wrote in message news:hsrvrh$317h$1(a)textnews.wanadoo.nl... >I know I shouldn't use lookupfields in tables. But does that also accounts >for when you create a lookup in a field's table from a 'list of values'? >For instance I want to create a lookup field for the field gender with >values "M" and "F". > > Thanks, Lars
From: Lars Brownies on 17 May 2010 15:26 > Users should NEVER see tables. I agree, but that was not my point. If you set the value list lookup in the table, the combo automatically appears whenever you put the field on any form. Lars "Arvin Meyer [MVP]" <arvinm(a)mvps.invalid> schreef in bericht news:OjGrD1e9KHA.420(a)TK2MSFTNGP02.phx.gbl... > Do it in a value list in a combo box in your form. > > Users should NEVER see tables. > -- > Arvin Meyer, MCP, MVP > http://www.datastrat.com > http://www.accessmvp.com > http://www.mvps.org/access > > > "Lars Brownies" <Lars(a)Browniew.com> wrote in message > news:hsrvrh$317h$1(a)textnews.wanadoo.nl... >>I know I shouldn't use lookupfields in tables. But does that also accounts >>for when you create a lookup in a field's table from a 'list of values'? >>For instance I want to create a lookup field for the field gender with >>values "M" and "F". >> >> Thanks, Lars > >
From: Arvin Meyer [MVP] on 19 May 2010 08:44 It takes less than a minute to add a combobox to a form. If you had 20 or 30 or more based on this field you might have a point. Five years from now, you or your successor will spend more than 20 minutes fixing things because it isn't clear how you've done it. That said, classically a table is used to store data, and maintain its integrity. How does this accomplish either of those goals? -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.accessmvp.com http://www.mvps.org/access "Lars Brownies" <Lars(a)Browniew.com> wrote in message news:hss5a0$1nt$1(a)textnews.wanadoo.nl... >> Users should NEVER see tables. > > I agree, but that was not my point. If you set the value list lookup in > the table, the combo automatically appears whenever you put the field on > any form. > > Lars > > "Arvin Meyer [MVP]" <arvinm(a)mvps.invalid> schreef in bericht > news:OjGrD1e9KHA.420(a)TK2MSFTNGP02.phx.gbl... >> Do it in a value list in a combo box in your form. >> >> Users should NEVER see tables. >> -- >> Arvin Meyer, MCP, MVP >> http://www.datastrat.com >> http://www.accessmvp.com >> http://www.mvps.org/access >> >> >> "Lars Brownies" <Lars(a)Browniew.com> wrote in message >> news:hsrvrh$317h$1(a)textnews.wanadoo.nl... >>>I know I shouldn't use lookupfields in tables. But does that also >>>accounts for when you create a lookup in a field's table from a 'list of >>>values'? For instance I want to create a lookup field for the field >>>gender with values "M" and "F". >>> >>> Thanks, Lars >> >>
From: Lars Brownies on 19 May 2010 10:52 I missed that point. Thanks for explanation. Lars "Arvin Meyer [MVP]" <arvinm(a)mvps.invalid> schreef in bericht news:#sxE8E19KHA.5012(a)TK2MSFTNGP02.phx.gbl... > It takes less than a minute to add a combobox to a form. If you had 20 or > 30 or more based on this field you might have a point. Five years from > now, you or your successor will spend more than 20 minutes fixing things > because it isn't clear how you've done it. That said, classically a table > is used to store data, and maintain its integrity. How does this > accomplish either of those goals? > -- > Arvin Meyer, MCP, MVP > http://www.datastrat.com > http://www.accessmvp.com > http://www.mvps.org/access > > > "Lars Brownies" <Lars(a)Browniew.com> wrote in message > news:hss5a0$1nt$1(a)textnews.wanadoo.nl... >>> Users should NEVER see tables. >> >> I agree, but that was not my point. If you set the value list lookup in >> the table, the combo automatically appears whenever you put the field on >> any form. >> >> Lars >> >> "Arvin Meyer [MVP]" <arvinm(a)mvps.invalid> schreef in bericht >> news:OjGrD1e9KHA.420(a)TK2MSFTNGP02.phx.gbl... >>> Do it in a value list in a combo box in your form. >>> >>> Users should NEVER see tables. >>> -- >>> Arvin Meyer, MCP, MVP >>> http://www.datastrat.com >>> http://www.accessmvp.com >>> http://www.mvps.org/access >>> >>> >>> "Lars Brownies" <Lars(a)Browniew.com> wrote in message >>> news:hsrvrh$317h$1(a)textnews.wanadoo.nl... >>>>I know I shouldn't use lookupfields in tables. But does that also >>>>accounts for when you create a lookup in a field's table from a 'list of >>>>values'? For instance I want to create a lookup field for the field >>>>gender with values "M" and "F". >>>> >>>> Thanks, Lars >>> >>> > >
|
Pages: 1 Prev: Pulling from three tables Next: Getting 'Smart Quotes' out of Access |