[AccessD] Access 101 question (I think)

John,

To me this sounds fine.  Generally, all lists should be modifiable in some
way by the program's users (except where you really know they won't change).

A question you might want to consider:  After a change is made, what will
happen to your reporting criteria.  If someone pulls up a report by
selecting one of the asian sub-groups, it will automatically not select
anything for a whole years' worth of data.  

When I have this issue, I present it to the users and ask them how they want
to handle it. 

HTH, 

Dan Waters


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Clark
Sent: Thursday, April 28, 2005 1:36 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Access 101 question (I think)

I am whipping up a quick program, and there are many "descriptors" in
the main table (i.e. hair, eyes, status, race, etc.). My question is
this:

Should I have an individual table for each descriptor? This is the way
I mostly do it now. I put in value lists for something like "gender,"
which will most likely stay the same (I don't want to think about the
"what ifs" here). But for other things, I like to leave it open for the
user to input. I then give them a button for "Program Administration"
and a bunch of little forms, which are basically prettied-up continuous
forms, to enter these options. 

This actually came in handy, on one of my previous programs. Their
"Race" designations were altered, about a year after they began using
the program...asian was split into sub-groups...and they were able to go
in and change this without my help. 

I was just wondering whether this is considered acceptable practice, or
if I am being a bit retentive here.

TIA 

John W Clark
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com