[AccessD] Design Question

Bryan,

Before you do anything you need to determine whether the DATES that you make
/ break these relationships matter (or any other info about the
relationship).  What Charlotte is discussing is a construct for data
warehouses, where data rarely if ever changes.  This does not sound like
your application.

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bryan Carbonnell
Sent: Wednesday, February 07, 2007 11:29 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Design Question

On 2/7/07, Charlotte Foust <cfoust at infostatsystems.com> wrote:
> I just skimmed John's reply, but no, that isn't exactly it.  A star 
> schema is commonly used in data warehousing and tables have a 
> multiplicity of FKs for all tables they relate to.  That makes 
> querying data a snap because you don't need complicated joins to get 
> the data you want, just filter on the FKs.

So in the people table there would be columns for the FKs for Software,
Hardware, Service  Agreements and Facilities. The equipment table would have
a column for the others, etc?

--
Bryan Carbonnell - carbonnb at gmail.com
Life's journey is not to arrive at the grave safely in a well preserved
body, but rather to skid in sideways, totally worn out, shouting "What a
great ride!"
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com