is there a way to make a composite attribute in access like a relational
database. That means can i have some attributes as subattributes of an
attribute.
e.g. there can be a column for address which may have sub-columns like
street, city, state etc. which may be referenced, say, by using a dot
operator or something. (just like as it is done in sql)

In relationnal database, normalization rule zero is that a field must be
atomic, must have just one value. If you need to tie other stuff, then the
RECORD, with its primary key, can be seen as an 'attribute' and each of its
FIELD can match what you described here as a sub-attribute.


Vanderghast, Access MVP


"abhinav2002" <(E-Mail Removed)> wrote in message
news:F34F1889-3CB0-4A24-B553-(E-Mail Removed)...
> is there a way to make a composite attribute in access like a relational
> database. That means can i have some attributes as subattributes of an
> attribute.
> e.g. there can be a column for address which may have sub-columns like
> street, city, state etc. which may be referenced, say, by using a dot
> operator or something. (just like as it is done in sql)

> In relationnal database, normalization rule zero is that a field must be
> atomic, must have just one value. If you need to tie other stuff, then the
> RECORD, with its primary key, can be seen as an 'attribute' and each of its
> FIELD can match what you described here as a sub-attribute.


thanks...
(you are right ... but i know this)
Actually I wanted to know that how is this done in Microsoft Access
(preferably 2003 if it makes a difference).
btw thanks again..

You can do it by making a new table in a one to one relation to your main
table, if you don't want to touch to your main table.

A one to one relation just impose a LIMIT of AT MOST one record in the child
table. It would be more convenient to call it a : one to (zero or one)
relation.

Vanderghast, Access MVP

"abhinav2002" <(E-Mail Removed)> wrote in message
news:B5CCB0DE-95C3-4A6A-84E2-(E-Mail Removed)...
>
>> In relationnal database, normalization rule zero is that a field must be
>> atomic, must have just one value. If you need to tie other stuff, then
>> the
>> RECORD, with its primary key, can be seen as an 'attribute' and each of
>> its
>> FIELD can match what you described here as a sub-attribute.
>
>
> thanks...
> (you are right ... but i know this)
> Actually I wanted to know that how is this done in Microsoft Access
> (preferably 2003 if it makes a difference).
> btw thanks again..

> You can do it by making a new table in a one to one relation to your main
> table, if you don't want to touch to your main table.
>
> A one to one relation just impose a LIMIT of AT MOST one record in the child
> table. It would be more convenient to call it a : one to (zero or one)
> relation.


Thanks mate..... i guess that should solve my purpose.