Kitting in Warehouse DB

[brsawvel]

Hello World,

I've been working on a DB for inventory purposes to keep track of certain IT equipment that my company will slap barcodes on. Sometimes we will have a server rack with a barcode that houses individual servers with their own barcodes.
I would like to "kit" them all together on a form with the rack being the "parent" asset (parent/child association) so that when I change the location of the "parent", all the "child" assets change location as well. But I would like to keep all the assets, "parent" and "child", on the same table for quantitative inventory purposes.
Any suggestions?

 

[MarkK]

Hey, welcome to the forum.
As a suggestion you can make a table that references itself. Each record will have it's unique ID field, and in addition each record has a foreign key field that may, or may not, reference a different record in the same table. Table might look like...

[B]tEquipment[/B]
EquipmentID (PK)
ParentID (FK) (if non-zero, represents an EquipmentID from this table)
EquipmentTypeID (FK) (type table not shown)
Manufacturer
Model