I Really Need Some Starting Guidance....

[znxm0i]

Hello All,

I could really use some help/direction in how to proceed with designing a table for an inventory database I want to setup. I am not understanding how to setup a "category" table properly. I want the category table to contain a category id # (autonumber) and a list of categories (i.e., basketballs, backpacks, water bottles, etc.). However, I want this table to cascade so that when the autonumber is expanded it will show all of the product items listed in the product table beneath the assigned category. The items in the product table are identified by a text product id code but need to be able to tie back to the category list.

Is this even doable? I am so lost....could someone please just help me get started?

Thank you

 

[spikepl]

1. Do a web tutorial on access table , queries and forms. 1 or 2 hours and so much wiser ...
2. Get a template for some exisiting database and see how it ticks. Microsoft have plenty of access templates : google that term
3. Having done all that, read this: http://allenbrowne.com/AppInventory.html

 

[plog]

However, I want this table to cascade so that when the autonumber is expanded it will show all of the product items listed in the product table beneath the assigned category.

Why? This isn't something you should do in tables, but should do with queries/reports. You should use tables like a bucket of memory--set it up properly, throw data into it and leave it alone. When you need to work with your data, you should use queries, forms and reports. Tables shouldn't have functionality other than storing data.

 

[GohDiamond]

Sounds like Category ID has to be a Foreign Key in your Products table where Product ID is the Primary Key

Then you establish a relationship between the Categories table and The Products Table based on the Category ID

Then when you open the Category Table there would be a [+] next to the Category ID of Backpacks, for instance, WHen you click on the + then list of all the backPacks should appear because of the RELATIONSHIP you established in the RELATIONSHIPs wizard.

Cheers
Goh

PS. I agree with plog and spikepl, but it's not unusual to establish a relationship between tables in such a case