10-02-08, 17:14 #1Registered User
- Join Date
- Oct 2008
Unanswered: Complex relationships with different tables
am creating a part numbering database for our small electronics firm. I have developed the part numbering scheme but, I am know looking to add specific components to a part number. Once you have entered the system it assigns a part number to you. I then have a menu to select the class of object (Mechanical, Electrical, etc ) then sub menu for category, then sub category till you get to the table that contains the component. How do I link the final table (component) to the original part number when you have travel several different tables to get to the final table and each part number could be assigned to a different component table? Each final component has a code that I want it to compare to other part numbers and their code to ensure I do not repeat a component under a different part number.
10-03-08, 00:13 #2L33t Helpa Munky
- Join Date
- Nov 2007
- Adelaide, South Australia
How do I link the final table (component) to the original part numberOwner and Manager of
CypherBYTE, Microsoft Access Development Specialists.
Microsoft Access MCP.
And all around nice guy!
"Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
"...teach a man to code and he'll be frustrated for life! " -- georgev
10-03-08, 04:24 #3Jaded Developer
Provided Answers: 59
- Join Date
- Nov 2004
- out on a limb
I think there are several different problems here
1 is the generation of the part number
2 is the associating back to the part
3 is making sure the part hasn't already been defined.
1 you reckon to have solved
2 depends on the way you have modelled your data (we'd need to see the table defintions to be sure.. but my guess would be you use relationships to associate a part with its constituent categories. a RI associatiation should handle that
3 is purely down to a mnual procedure, unless you part definition is that tight that you can derive its a duplicate part becasue the category data is similar.
if the component code is made unique (create an index for that code) then you can ensure that from a systems perepective its unique, but yoiu can from a human perspective short of doing manual checks). Ive dsigned systems in the past where you force a user to search the db to look for duplicates (typos and the like). you cna use tools such as soundex or other metaphone based tools... although they are designed for predominantly anglo saxon/ western surnames they can be very good.. Izyrider as a double somehtign or other which he claims gives better results than soundex.I'd rather be riding on the Tiger 800 or the Norton
10-04-08, 00:34 #4Registered User
- Join Date
- Oct 2004
- Melbourne, Australia
Could you please clarify just what the part number refers to. It could be the component itself and that component belongs to a particular node in a tree of objects (class, category, etc.), or the component can belong to several different trees and can have a different part number in each family situation.
In the first case, the part number would be assigned to the component when first entered and the component would then be assigned to whatever trees it is a member of afterwards. In the second case, the part number would be assigned to the component after traversing the tree, so that the part number not only identifies the component, but also the hierarchy it is a member of.
Which is it ?