ms access - When to use lookup field? -


whenever i'm considering option of making field's contents being extracted predefined list, should make new table list exclusively options, make query, make form-level lookup field select it?

this seems creating lot of tables , queries tables, have lookup field. have no idea normal number should be, or if there clever way of doing queries without creating new tables everytime i'm not aware of.

for example: have addresses table, , each address can of 3 types: home, professional, other. should make table exclusively list items , reference through query , lookup field in form?

what's procedure here? in advance!

use table lookup when going use lookup in entity or going allow end-user edit entries of lookup. in other cases, free confine use constant list of values.

feel free ask more.


Comments

Popular posts from this blog

javascript - Karma not able to start PhantomJS on Windows - Error: spawn UNKNOWN -

c# - Display ASPX Popup control in RowDeleteing Event (ASPX Gridview) -

Nuget pack csproj using nuspec -