Long,
This is what access was made to do. The structure would take too long for me
to write out here, but the basic method, is that you have a table for
products, table for subproducts, table for subsubproducts and so on. in
subproducts you have a field to say which produt it is for, and in
subsubproducts you have a field to say which subproduct it is for. THis is
whats called a one-to-many relationship. I suggest you read up on this and on
access in general and how to structure it should become fairly obvious.
O and have a look at the northwind database, which comes with access, it is
a perfect example of a ordering/parts database
> I am trying to create a database that will be able to track inventory of
> products that are used to make up different items. Basically we are building
[quoted text clipped - 11 lines]
> monitor the items. Am I making any sense to anyone? Is this all logical to do
> in access? Thanks for any help anyone can give.
Long - 30 Jan 2008 01:24 GMT
Thanks. If I have additional questions will you be willing to work with me?

Signature
Long
> Long,
>
[quoted text clipped - 24 lines]
> > monitor the items. Am I making any sense to anyone? Is this all logical to do
> > in access? Thanks for any help anyone can give.