is there a need for lookup table

[Qamar]

Hello

I have a combobox on a form where you can select a year. In this circumstance is it overdone to have a lookup table (YearID and YearofIssue) for this field rather than simply have a combobox with a value list?

Thanks

 

[namliam]

I think in case of ANY combo that has a growing list or possibly subsequent uses, you will want a lookup table...

Tho in the case of year, It is not a growing list (I mean it isnt infinate and you can easily take care of adding the years into the rowsource without having a table in place).
Also Year dont have (much) subsequent uses I can see right of the bat....

So I would say, no.... dont use a lookup table. And Yes it is overdone IMHO.

 

[Qamar]

Hello

Thank you for replying. I agree with what you said, but in my circumstance i don't want to put all the range of years which i may use, as i wish to only use the years that i have records for and then populate other years if any new records would require them. For example if i don't have any records from year 2000 it should not be in my list, then if a new record needs it, it will be added from the OnNotInList event.

So in this case, do you think it is still overdone?

Once again, thank you for your assistance.

 

[namliam]

That would depend your the size of your "needed" records.

You can do a select distinct year from your table to fill the combo without using a lookup table. Tho that works best if you dont have any performance issues.