Value List or seperate table?

[HockeyNut]

Another one of my "Best Practice" kind of questions.

If I have 7 values in a value list, which I'm 99% sure wont change over time. Is the best practice still to create a seperate table (to be used as a lookup)?

HN

 

[Mile-O]

I would prefer to put the 7 options in a table as you say yourself you are not 100% sure that it won't change over time.

I only use a value list if I know that the list isn't going to change i.e. Yes - No - N/A, Monday through Sunday, Months, etc

 

[HockeyNut]

I was 99% certain that would be the case. lol

Thanks for the reply Mile

 

[namliam]

Instead of creating a multitude of tables for stuff like this, you can have 1 table containing different values for different comboboxes with 1 added field (number or text) to select which list to show.

just my $0.02

Regards

 

[Mile-O]

Instead of creating a multitude of tables for stuff like this, you can have 1 table containing different values for different comboboxes with 1 added field (number or text) to select which list to show.

Do you mean a table with this structure?

tblLookups
Fruit
Vehicles
Countries
etc...


If so, the lists may vary in length creating redundant cells.

If not, what do you mean?

 

[Graham T]

This thread by Pat may help:

http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=52876&highlight=combo+and+list

Graham

 

[namliam]

Mile i do mean something like Pat suggested...

Regards