Re: Simple question on data design...

Heinz and David,

thanks for your very helpful replies.
With my 3 months part time experience in database management systems design (read: MS Access), it is good to learn more all the time.

Further decomposing the table makes sense to me depending on other factors as mentioned...

I will consider both responses carefully.

kind regards,

Zigler after a bad day

Ken Zigler <reply_at_group.please> wrote in message news:6TmG7.256$UW5.202030_at_news.uswest.net...
> Hello, group.
>
> Consider tables with columns that contain data from
> a limited, pre-set list or domain, such as:
>
> tblAddresses (AddressID, ClientID, Street, City, State, Zip, AddressType)
>
> where the attribute AddressType could be one of the following:
>
> Primary
> Billing
> Shipping
> Location
>
> (disregarding whether this is a good model or not) ...one could store
> the data as shown above, or each value could be represented
> by a single letter. The single character value could save space,
> but requires more work when displaying the data in a meaningful
> way (by substituting the word represented)... Other similar scenarios
> would include attributes like ShippingMethod, PaymentType, Gender,
> etc...
>
> Is there any logic that suggests one approach over the other?
>
> many thanks for any suggestions,
>
> Zigler
>
>
>
Received on Fri Nov 09 2001 - 00:45:18 CET