![]() ![]() This is another opportunity for me to regret not keeping the tables manual when I retired as it was a 2" thick binder duplex printed list of all the tables and fields info. AFAIK, none of this was done via recursive methods, rather it was table design. All the tables were in some type of sql server db and Access was the query tool. I used to work with a CMMS system that contained a BOM component. I've tried searching, but BOM is too short a search term, and "Bill Material" (the of also being too short to use for searching) does not seem to find any examples. So, I'm left with a single table that has a part and a reference to a higher level part, that relationship being a piece part into an assy, or a sub-assy into a higher level assy or product. Each product could have a common component in multiple sub-assy's as well as those sub-assy's at different levels of the BOM so not easy to just set up tables for simple parts (which actually have subs which are the raw material), first level sub-assy's, second level sub-assy's, etc. I am looking to have a table that self-references - a part can be a component of another part (assy), which in turn can be a component of a higher level assy, which in turn can be a component in a higher level assy. This must be a normal use of a database (individual part used in assy's - seems like the classic one to many relationship situation), but I'm not finding any samples/examples. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |