[AccessD] Code Tables

>I think it was pretty standard for all the xBase languages because it was
so hard to keep track of all the table files otherwise.

LOL.  I got a job one time rescuing a Paradox database that was crumbling.
It had well over TWO THOUSAND files in dozens of directories.  It was not
pleasant trying to get the data out of it.

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Tuesday, April 24, 2007 11:58 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Code Tables

I seem to recall we did it that way in dBase too.  I think it was pretty
standard for all the xBase languages because it was so hard to keep track of
all the table files otherwise.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert L.
Stewart
Sent: Tuesday, April 24, 2007 8:51 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Code Tables

He is probably an ex-FoxPro developer.
They were one of the ones that got into
doing a single table like that for all
of the lookups.

It is flat out bad design.

Show him the correct way, yours.

Robert

At 10:22 AM 4/24/2007, you wrote:
>Date: Tue, 24 Apr 2007 09:59:55 -0400
>From: "Tesiny, Ed" <EdTesiny at oasas.state.ny.us>
>Subject: [AccessD] OT a little - Code Tables
>To: <dba-ot at databaseadvisors.com>,      "Access Developers discussion
and
>         problem solving"        <accessd at databaseadvisors.com>
>Message-ID:
> 
><F7F17F79CF2A60418DC957FA11069BC71216A9 at ALBMX2K3.rt.oasas.state.ny.us>
>Content-Type: text/plain;       charset="us-ascii"
>
>Hi All,
>I'm not familiar enough with SQL Server but I have a question regarding

>what I call Code Tables.  I use them a lot when I develop an 
>application in Access, e.g., I'll have a table for counties i.e., 
>county code and county name or Providers, Provider code and Provider 
>Name.  I have them as separate tables.  I'm trying to make sense out of

>the tables and relationships "my" programmer created.  He has one code
table period!
>Below is a look as to how it is setup.
>
>dbo_tblCodes
>CodeType        CodeId  CodeName        OrderOnForm
>Ethnicity       1       Puerto Rican    1
>Ethnicity       2       Mexican 2
>Ethnicity       3       Cuban   3
>Ethnicity       4       Other Hispanic  4
>Ethnicity       5       Hispanic, Not Specified/Known   5
>Ethnicity       7       Not of Hispanic Origin  6
>Ethnicity       9       Don't Know/No Answer    7
>Gender  1       Male    10
>Gender  2       Female  20
>Health  1       Poor    5
>Health  2       Fair    10
>Health  3       Good    15
>Health  4       Very Good       20
>Health  5       Excellent       25
>Health  9       Don't Know/No Answer    80
>
>This is just a little bit of the table but I think you can see his 
>"logic" here.  Is this a common convention that developers use?  Hate 
>to see what else I'm going to find as I try to wade through this.
>TIA
>Ed
>
>
>Edward P. Tesiny
>Assistant Director for Evaluation
>Bureau of Evaluation and Practice Improvement New York State OASAS 1450

>Western Ave.
>Albany, New York  12203-3526
>Phone:  (518) 485-7189
>Fax:  (518) 485-5769
>Email: EdTesiny at oasas.state.ny.us


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

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