[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: [OT] Access Database Question
Hmm... not sure,
Not sure a) how to do that, or, b) what the point of it would be...
there are lots of values of potential household addresses, but only ever
a few member records to link to any given one... I'm not sure how moving
their address fields out to a separate table helps... - Although I'm
willing to give it a try I guess...
Strikes me that this should be *really* simple to do though, - there
must be loads of cases where you only want to view unique values within
a table...
Paul G.
-----Original Message-----
From: ukha_d@xxxxxxx [mailto:ukha_d@xxxxxxx] On Behalf
Of Jon Whiten
Sent: 10 August 2008 15:09
To: UKHA Group
Subject: Re: [ukha_d] [OT] Access Database Question
Would it be too much stress to create a Household table and then link
that
to each member? A bit of one-off work up front.
;oj
On 10/08/2008, Paul Gordon <paul@xxxxxxx> wrote:
>
> Snip
>
> The next step I want to do is to generate a table that contains only
> unique addresses; - since there are in many cases multiple members at
> the same address. Since every individual has a member record, the
query
> above will include multiple records for some addresses. - I want to
have
> a table that only shows any given address once, so that I can produce
a
> list of households, rather than individuals...
>
> Got any suggestions on where to start looking?
> .
>
>
>
[Non-text portions of this message have been removed]
------------------------------------
UKHA_D Main Index |
UKHA_D Thread Index |
UKHA_D Home |
Archives Home
|