[AccessD] normalization question

I just did this for a potential client.  It started out with an email
they sent describing what they wanted from the application.  I analyzed
it and took into account what I knew about their organization.  I then
put together an ER diagram and a long-hand list of tables, fields,
types, and notes regarding keys.  This is what I presented the client
with as my base starting point.  We discussed it and they made
suggestions and/or clarifications on some of the points.  As soon as
they sign the contract, I'm ready to run with it with little or no table
modification from here on out.

Seth

On Mon, 2003-03-10 at 13:10, Mwp.Reid at Queens-Belfast.AC.UK wrote:
> When making the list before its finalised. I would generally take the user or 
> who ever over the diagrams etc and get agreement before actually doing anything.
> 
> FKs etc all go in to the diagrams. That way you dont forget to do them when you 
> come to build the tables.
> 
> Martin
> 
> Quoting Susan Harkins <harkins at iglou.com>:
> 
> > Yes, I agree...
> > 
> > but in the process of making your paper lists -- when?
> > 
> > 
> > ----- Original Message -----
> > From: <Mwp.Reid at Queens-Belfast.AC.UK>
> > To: <accessd at databaseadvisors.com>
> > Sent: Monday, March 10, 2003 1:34 PM
> > Subject: RE: [AccessD] normalization question
> > 
> > 
> > >
> > > you do it before turning the PC on when your designing the structures.
> > The
> > > theory is that the data is normalised before you actually create the
> > tables
> > > physically.
> > >
> > > Martin
> > >
> > > (<:
> > >
> > >
> > >
> > > Quoting Charlotte Foust <cfoust at infostatsystems.com>:
> > >
> > > > I tend to do it at the time so I don't forget.  Of course, as we
> > get
> > > > older our memory ... Uh, what was I saying?  <vbg>
> > > >
> > > > Charlotte Foust
> > > >
> > > > -----Original Message-----
> > > > From: Susan Harkins [mailto:harkins at iglou.com]
> > > > Sent: Sunday, March 09, 2003 3:36 PM
> > > > To: AccessD at databaseadvisors.com
> > > > Subject: [AccessD] normalization question
> > > >
> > > >
> > > > When you remove a field to another table (for whatever reason), do
> > you
> > > > immediately create the foreign key in the original table, or do
> > you
> > > > wait
> > > > until you've completely normalized each table and then return to
> > the
> > > > tables and insert all the foreign keys then?
> > > >
> > > > I tend to do it later because the nature of a single field can
> > change.
> > > >
> > > > Does anyone know if the relational model requires a particular
> > > > routine?
> > > >
> > > > Just curious.
> > > >
> > > > Susan H.
> > > >
> > > > _______________________________________________
> > > > 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
> > > >
> > > _______________________________________________
> > > 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
> > 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
-- 
Seth Galitzer			sgsax at ksu.edu
Computing Specialist		http://puma.agron.ksu.edu/~sgsax
Dept. of Plant Pathology
Kansas State University