1 to 1 relationship with multiple tables
I have 3 tables: Tag Library - A table containing barcode information for thousands of pre-printed tracking tags Item Type A - Table of type A items which will be tagged using tags from the Tag Libr...
Forum Discussion
Sohum, could the type A/B be a field in lieu of two distinct tables? It seems to me that you need an Items Table and a Tag Table and those could be related. You could set a "unique field" on the barcode to ensure it is not used twice.
------------------------------
Ivan Weiss
------------------------------
------------------------------
Ivan Weiss
------------------------------
Hi Ivan,
Unfortunately, I don't think they can. Type B products are created from Type A products so there is a 1-M parent-child relationship between those tables.
------------------------------
Sohum Shah
------------------------------
Unfortunately, I don't think they can. Type B products are created from Type A products so there is a 1-M parent-child relationship between those tables.
------------------------------
Sohum Shah
------------------------------
- hmmm not sure I am following this from a design perspective.... So are you saying that Type A gets a barcode and might be part of Type B which also gets a different bar code?
------------------------------
Ivan Weiss
------------------------------- Type A products are what I would call a "mother" and require a tag.
Type B products start as a small part of a "mother" and are processed/built from there, but also require individual tags, as well as the ability to determine which "mother" tag/Type A product it originated from.
Hope that helps clear it up
------------------------------
Sohum Shah
------------------------------
