Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Recent content by Griphus

  1. Griphus

    Best structure for lots of yes/no's?

    Yes, your understanding is very close. A Component for a project has Operations associated with it. A Routing (also called a Production Order) has a list of Operations that will be performed either on a Component or to make a Component. Correct, Operations take time to complete (as opposed...
  2. Griphus

    Best structure for lots of yes/no's?

    Got it. Thanks. I've got the options table built and I'm filling it in right now. We have something like 80 "options." Is there something more I can tell you about our time entries that would help you understand? I could show you some very limited part of the dataset or something if it...
  3. Griphus

    Best structure for lots of yes/no's?

    Hey there, Thanks very much for the response. If you were asking me to verify that any one project has only one model, enclosure type, application, customer, end user. Yes, that is correct. (One project can only have one voltage, diameter, length, number of poles, noise limit, etc. I've...
  4. Griphus

    Best structure for lots of yes/no's?

    I was worried that would happen. ;-)
  5. Griphus

    Best structure for lots of yes/no's?

    Thanks for the reply - I try to keep my posts relatively short & to the point out of respect for your time. I don't know where else I would get this information if not here, so I try to do whatever I can to make an answer as likely as possible. :-) Based on your suggestion, I typed this up...
  6. Griphus

    Best structure for lots of yes/no's?

    I should clarify that I have used junction tables (once) in the past... but didn't have to build any forms, etc for that database because it was just a work in progress for my personal use. My understanding is that I would have one very large lookup table of all options - maybe 3 fields (ID...
  7. Griphus

    Best structure for lots of yes/no's?

    So, I understand what you are both saying... but I run into an issue because going forward I won't understand how to work with the data. That is, I won't know how to build a form where a user can put in the data, and I won't know how to use the data the user put in once it's in the database...
  8. Griphus

    Lookup Table "Best Practices"

    Thank you both for the answers. Much appreciated. :-)
  9. Griphus

    Best structure for lots of yes/no's?

    Hello, Currently working on a database for a "somewhat standard" product with lots of options customers can purchase. Options are almost all "yes/no" type, with a smattering of "if yes, how many" type scenarios. Database uses the product serial number as the primary key. So, is the best way...
  10. Griphus

    Lookup Table "Best Practices"

    At the risk of being too audacious, a "why" for any answers / opinions would also be awesome so we can educate ourselves. Teach a man to fish and all that... :)
  11. Griphus

    Lookup Table "Best Practices"

    Hi! A coworker and I are having a debate about the most correct way to do something. I'll attempt to describe this as objectively as possible. :-) We have a database with several lookup tables. This is for building motors, so the tables are for things like bearings, the enclosure for the...
  12. Griphus

    Any way to use logic & procedural decisions in database design?

    I have a question about this statement. I understand what you mean philosophically, but not how to implement it. As an easy example... say we have a motor, and the customer has an option to buy a cooler or not buy a cooler. Once they've bought a cooler, they can choose 0, 1, or 2 liquid level...
  13. Griphus

    Any way to use logic & procedural decisions in database design?

    Hi MajP, Regarding the first part of your post, that is exactly correct. The left column is a list of all the possible selections (51 of them). The blank can be filled in with a C or an E (don't know why he created it that way...). I will work on creating the table you mention in the second...
  14. Griphus

    Any way to use logic & procedural decisions in database design?

    No sir... I'm essentially building it from scratch as we "speak." Right now I'm still working on cleaning up all sorts of other inconsistencies in the data set.
  15. Griphus

    Any way to use logic & procedural decisions in database design?

    I agree with you regarding data storage philosophy, but no, essentially I'm dealing with a giant flat-file that someone put in Access and I'm trying to turn it into a proper relational database.
See more

Part and Inventory Search

Back
Top