[AccessD] Normalisation

...if it has to be "working" by tomorrow, build it flat and focus on the
user interface and data validation ...you can always normalize later if
necessary ...not the way anyone likes to do these things but we all have
faced similar demands at one time or another ...HTH :)

...btw, you haven't told us lately just when the wedding date is :)

William Hindman
"And so, my fellow Americans: ask not what your country can do for you - ask
what you can do for your country. My fellow citizens of the world: ask not
what America will do for you, but what together we can do for the freedom of
man." John F. Kennedy, 1961

----- Original Message -----
From: "Roz Clarke" <roz.clarke at donnslaw.co.uk>
To: <accessd at databaseadvisors.com>
Sent: Monday, March 17, 2003 5:36 AM
Subject: RE: [AccessD] Normalisation


> Martin
>
> Yes people can make multiple claims over time. The claim can be one of 2
> types (different policy types). Each claim is likely to have multiple
calls
> but these are already logged in a generic call log database (the databases
> are interconnected through the user interface). All I'm interested in at
the
> moment is the info describing the claim.
>
> The call centre will not be taking calls directly from the client, but
from
> the local branch of their insurance company (we handle claims registering
> for a number of different insurers). Therefore there should only be one
set
> of details per accident, as any passengers claiming will be claiming
against
> the policyholder's insurance - and the claim will generally have passed
out
> of our hands before anything like that gets processed anyway.
>
> Because of the way they work, if there were to be more than one claim per
> accident, they'd want the accident details duplicating anyway.
>
> Clear as mud?!
>
> Roz
>
> PS did I mention I have to have this built by tomorrow?
>
> -----Original Message-----
> From: Mwp.Reid at queens-belfast.ac.uk [mailto:Mwp.Reid at queens-belfast.ac.uk]
> Sent: 17 March 2003 09:59
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] Normalisation
>
>
> Roz
>
> People can make mulitple claims over a period of time. The claim is opf a
> specific type. Am I missing something?
>
> The claim then could have multiple calls etc associated with it (Unless
your
> a
> better insurance ocmpany than mine)
>
> Claims could come in from multiple parties. i.e carsh carsh and everyone
in
> the 20 seater MVPV makes a claim.
>
> Martin
>
>
> Quoting Roz Clarke <roz.clarke at donnslaw.co.uk>:
>
> > Hey all
> >
> > I have a bit of a funny database spec for a call centre application
> > (callers ringing to register insurance claims).
> >
> > The details taken from the customer cover a lot of different entities;
> > the caller, their insurance policy, their car, the accident, the third
> > party,
> > the third party's car, the third party's insurance policy etc. My
> > instinct
> > is to create a table for each distinct entity. However, they will all
> > have
> > 1:1 relationships as there is only one instance of each entity per
> > claim
> > (the caller I would hold separate as we may handle more than one claim
> > for
> > them). This is a fairly 'disposable' (i.e. expected to be used only in
> > the
> > short term and never to be expanded) app. Would it be shockingly bad
> > behaviour just to stuff everything into one table??
> >
> > Roz
> >
> _______________________________________________
> 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
>