quick database design assistance needed (access db)

greetings all... I know this is more of a db question, but I'm hoping
that my fellow asp folk will take pitty on me and help me out.
If someone could provide me with some insight as to how I should break
up and normailze these tables I'd be most appreciative. I am
struggling with putting my own tables in order, although I do
understand the concepts of normaization.

Thanks

handpieces table
-----------------------------
handpieceID
name
category
systemsID
ezfixID
manufacturer
shortDesc
longDesc
chuckType
handpieceSpeed
handpieceIMG
handpieceConnection

systems table
---------------------
systemID
name
modelNumber
category
shortDesc
longDesc
priceNew
priceSpecial
priceTradein
priceDiscount10
priceDiscount5
warrantyNew
warrantyOther
manufacturer

Here is where I see redundancy...

I will have handpieces that will belong to multiple systems. If I am
to only have indovidual handpieces in the handpieces table (primary key
is handpieceID), what table shoudl I create to repesnet the
relationship to systems.

Thanks

Re: quick database design assistance needed (access db)

Because you're dealing with a many-to-many relationship (i.e. the most
complicated kind of relationship) sounds like you need a linker table
with systemID field and handpieceID field.

Best regards,
-Paul
www.Bullschmidt.com - Freelance Web and Database Developer
www.Bullschmidt.com/DevTip.asp - Classic ASP Design Tips


josephweiss@gmail.com wrote:
> greetings all... I know this is more of a db question, but I'm hoping
> that my fellow asp folk will take pitty on me and help me out.
> If someone could provide me with some insight as to how I should break
> up and normailze these tables I'd be most appreciative. I am
> struggling with putting my own tables in order, although I do
> understand the concepts of normaization.
>
> Thanks
>
> handpieces table
> -----------------------------
> handpieceID
> name
> category
> systemsID
> ezfixID
> manufacturer
> shortDesc
> longDesc
> chuckType
> handpieceSpeed
> handpieceIMG
> handpieceConnection
>
> systems table
> ---------------------
> systemID
> name
> modelNumber
> category
> shortDesc
> longDesc
> priceNew
> priceSpecial
> priceTradein
> priceDiscount10
> priceDiscount5
> warrantyNew
> warrantyOther
> manufacturer
>
> Here is where I see redundancy...
>
> I will have handpieces that will belong to multiple systems. If I am
> to only have indovidual handpieces in the handpieces table (primary key
> is handpieceID), what table shoudl I create to repesnet the
> relationship to systems.
>
> Thanks