>I know this is more of a business-logic question, but I was just wandering how anyone represents a lookup list, the lists are all held in seperate tables and usually have the odd difference.
>
>Do you just create a BO for each lookup list?
>
>I know this isn't a straight-forward answer, but an example would be lovely.

My overloaded Lookuplist table has three fields, LookupID(I Primary Key), LookupType(C10), and Entry(C20). A local view of it has a LookupType parameter, to grab whichever group is needed. A custom Combobox uses the application object's Lookup bizobj (or instantiates one), requeries the view for combobox.lookuptype, and stores the results (Entry, LookupID) to the combobox's aElements array. Any other table needing a lookup value has a namedID integer that matches the LookupID.

Hope it helps, ask if there's anything that needs more explanation.

Chris.