Thanks Vincent I going to give it a try. It seems pretty simple to
implement.

Vincent Johns wrote:
Tina's "miscellaneous" Table has worked well for me, too. This is one
case in which having dozens of unrelated fields in a record makes a
lot of sense. I do try to give the fields suggestive names (not
"Value1", "Value2", etc.) and of course I add comments (in Table
Design View) to provide some explanation of what the datum means. (Those
comments are not just for someone else's benefit -- it also
helps me, six months or more later.)

-- Vincent Johns
Please feel free to quote anything I say here.

tina wrote:

[...]
if this is what you're talking about, then read on for the solution
i use: i sometimes find myself with a few "miscellaneous" values
that are used in various places in my database but don't really
"belong" in any of my data tables. when that happens, i create a
miscellaneous table, with *only one record* (if you find that you
need multiple records of one value, then that's a legitimate table
that should be built as such), and a separate field for each value
that i need to store. the table is not linked to any other table,
and the fields in the table usually don't have anything to do with
each other. having built and populated tblMisc, you can retrieve a
particular
value wherever you need it in your database, with a simple DLookup()
function - remember that the table has only one record in it, so all
you need to do is look up the field holding the value you're after,
as DLookup("ThisField", "tblMisc")

hth

--

Joe Cilinceon