J
Joe Miller
Hi,
I'm having a bit of a mind meltdown at the moment and need someone's expert
advice on how to circumvent a little problem.
Essentially, I have a table which lists the dates of appointments [ApptDate]
for people [Name] with a booking ID [BkgID] which is an autonumber field and
the primary key. People can however be given an appointment together,
essentially meaning that Record 1 and Record 2 could represent the same
appointment booking, but for two different people. The grouped people are
linked by an identifying code [VSOID] which is neither a key field, nor
contained in a separate table. The matter is further complicated by the fact
that a person or group of persons may return for more than one appointment
meaning that the [VSOID] field is likely to reccur not just for the same
group of people but for different apoointment dates.
I want to collect information about each appointment from other fields in
the table, but only counting each appointment once.
I'm sure that there's some shocking examples of bad normalisation here, but
I'm not a professional and its one of those systems that started small and
grew big.
I was working on the basis of creating a concatenated field with the
[ApptDate] and [VSOID] fields but from there I've drawn a blank.
Can anyone point me in the right direction? More is the point, can anyone
understand me?
Thanks
Joe
I'm having a bit of a mind meltdown at the moment and need someone's expert
advice on how to circumvent a little problem.
Essentially, I have a table which lists the dates of appointments [ApptDate]
for people [Name] with a booking ID [BkgID] which is an autonumber field and
the primary key. People can however be given an appointment together,
essentially meaning that Record 1 and Record 2 could represent the same
appointment booking, but for two different people. The grouped people are
linked by an identifying code [VSOID] which is neither a key field, nor
contained in a separate table. The matter is further complicated by the fact
that a person or group of persons may return for more than one appointment
meaning that the [VSOID] field is likely to reccur not just for the same
group of people but for different apoointment dates.
I want to collect information about each appointment from other fields in
the table, but only counting each appointment once.
I'm sure that there's some shocking examples of bad normalisation here, but
I'm not a professional and its one of those systems that started small and
grew big.
I was working on the basis of creating a concatenated field with the
[ApptDate] and [VSOID] fields but from there I've drawn a blank.
Can anyone point me in the right direction? More is the point, can anyone
understand me?
Thanks
Joe