A db of customized containers...not sure how to design this one

[hihihi]

Suppose I have a db of products. Each of these products can select
from a number of features. Each of those features can have
subfeatures. Etc.

So I have a table of Products.
A table of level one features (product features).
A table of level two features (feature features), etc.

What I want to be able to do is open a record and create a custom
product.

I open a record, select a product name.

Then I select a feature that product contains. For that feature I
select a subfeature.

Then I select another feature that product contains. For that second
feature, I select another subfeature.

And so on.

My question is I'm not sure how to do a table design that can handle
this. I know that I need junction tables. But how do I make it so
that I keep track of all this? Can someone describe a schema that
would handle this type of database?

Many thanks,
Jimmy

 

[Steve]

TblProduct
ProductID
<ProductFields - NOT FEATURE FIELDS>

TblFeature
FeatureID
<Feature Fields - NOT PRODUCT FEATURE FIELDS>

TblFeatureFeature
FeatureFeatureID
<FeatureFeature Fields - NOT PRODUCT FEATURE Feature FIELDS>

TblProductFeature
ProductFeatureID
ProductID
FeatureID

TblProductFeatureFeature
ProductFeatureFeatureID
ProductFeatureID
FeatureFeatureID

If you need help setting up your database, I can help you for a nominal fee.
Contact me.

Steve
(e-mail address removed)

 

[Piet Linden]

Suppose I have a db of products.  Each of these products can select
from a number of features.  Each of those features can have
subfeatures.  Etc.

So I have a table of Products.
A table of level one features (product features).
A table of level two features (feature features), etc.

What I want to be able to do is open a record and create a custom
product.

I open a record, select a product name.

Then I select a feature that product contains.  For that feature I
select a subfeature.

Then I select another feature that product contains.  For that second
feature, I select another subfeature.

And so on.

My question is I'm not sure how to do a table design that can handle
this.  I know that I need junction tables.  But how do I make it so
that I keep track of all this?  Can someone describe a schema that
would handle this type of database?

Many thanks,
Jimmy

you might try doing subclassing. Rebecca Riordan has an article about
it on Access web.
http://www.mvps.org/access/tables/tbl0013.htm

 

[John... Visio MVP]

If you need help setting up your database, I can help you for a nominal
fee. Contact me.

Steve
(e-mail address removed)

These newsgroups are provided by Microsoft for FREE peer to peer support.
There are many highly qualified individuals who gladly help for free. Stevie
is not one of them, but he is the only one who just does not get the idea of
"FREE" support. He offers questionable results at unreasonable prices. If he
was any good, the "thousands" of people he claims to have helped would be
flooding him with work, but there appears to be a continuous drought and he
needs to constantly grovel for work.

A few gems gleaned from the Word New User newsgroup over the Christmas
holidays to show Stevie's "expertise" in Word.


Dec 17, 2008 7:47 pm

Word 2007 ..........
In older versions of Word you could highlght some text then go to Format -
Change Case and change the case of the hoghloghted text. Is this still
available in Word 2007? Where?
Thanks! Steve


Dec 22, 2008 8:22 pm

I am designing a series of paystubs for a client. I start in landscape and
draw a table then add columns and rows to setup labels and their
corresponding value. This all works fine. After a landscape version is
completed, I next need to design a portrait version. Rather than strating
from scratch, I'd like to be able to cut and paste from the landscape
version and design the portrait version.
Steve


Dec 24, 2008, 1:12 PM

How do you protect the document for filling in forms?
Steve


One of my favourites:
Dec 30, 2008 8:07 PM - a reply to stevie
(The original poster asked how to sort a list and stevie offered to create
the OP an Access database)

Yes, you are right but a database is the correct tool to use not a
spreadsheet.

Not at all. If it's just a simple list then a spreadsheet is perfectly
adequate...




John... Visio MVP

 

[Piet Linden]

These newsgroups are provided by Microsoft for FREE peer to peer support.

Drat!!! I was hoping I could have people send me money via a PayPal
account... is that why linking to this doesn't work? <j/k!>