Hi everyone,
With all your help, I did such a great job with the one DB project (for LCM for parts) that this past Friday, my boss has tasked me with another one. Actually, he wanted this project done in Excel, but with 3100 records and counting, I don't believe that is wise.
The project is to create a database that will track ECOs (Engineering Change Orders) by model number (in some cases, an ECO will cover a family of models). It seems that several attempts have been made to do this over the past 20 years, and in each case, the person in charge has given up in frustration. I've been importing ALL the information from the six separate spreadsheets from previous attempts into one (for the time being). Each record must contain the ECO #, the date, the drawing number (this has multiple numbers in this cell), a component number, model number, serial number, work order number, a .pdf copy of the ECO and status (Active or Void).
The objective is that when running a query on the model, all ECOs will appear within the query. Sounds simple, but there are a couple of extenuating circumstances:
- An ECO can list changes in several models that have a familial connection (XYZ model, Rev 1, Rev 2, etc.),
- Also, an ECO can list changes in several families of models that share assemblies (the bottom plate assembly for XYZ model, Rev 1; is used in DEF model, Rev 7).
So, I'm wondering if I need to set up a separate record for each ECO to each model/version (one to one); or one ECO to all the model/families (one to many) or if I can get away with making one record of all the ECOs to each model, version (many to one).
Any assistance, advice or even telling me how to do this, would be greatly appreciate. And if you're in the Los Angeles, OC or IE areas; I'll send you brownies as a thank you gift!