boolean data values or 2 row item lists

[shkspeare]

I've always used boolean values in tables, and then client-side code to get the corresponding text value.. (e.g. 0='open', 1='closed').

if me.boo = 0 then
 me.textbox = 'open'
else 
 me.textbox = 'closed'
end if

Are there any arguments for using table(s) to store these? I'd assume the additional Joins would be more overhead, and slower then the client side code to get the text value.

Tblist1
id  value
01 Open
02 CLosed

Select M.name, L.value from mainTbl
left join Tblist1 L on M.ID = L.id

There are several other similiar data points like this.


Working 1st time with a remote DB, so of course speed is concern. Using both Local tables and remote i hear will cause odbc to slow JOINS.


thanks!

[June7]

Only advantage for table would be if you want flexibility in adding value options, such as "Pending". If there can never be more than 2, then I would not bother with lookup table.

The VBA will not work nice with form in continuous or datasheet view. Programmatically setting value of unbound textbox will show the same value on all records. Use expression in textbox ControlSource so result will be dynamic for each record.

I would use a multi-column combobox (with Value List) instead of a textbox so there is one control for data entry/edit and display.

In either case, no VBA needed.