Search results

  1. K

    Nested junction tables

    The attached shows what I understand you are saying, Simon. Option A seems to be the easiest, but option B would make the combo box selections cleaner when relating products to Models, et al. It looks like I would have one record for each model/customer/location combination in option B...
  2. K

    Nested junction tables

    Hmm...So if I undertand correctly the process would be to assign a Model to a Location, the assign the Model-Location to a Customer. I could then assign the whole lot to a Product? I think product could be first or last in the process because it has the one to many relationship with everything...
  3. K

    Nested junction tables

    Yes, the model is unique to the customer and built in several locations. Yes No, if you mean customers share model numbers. No problem, they order from each location by customer. Ok I'm not sure how to anwer this one, maybe with an example? Please forgive the pseudonyms; an ultra-strict...
  4. K

    import from excel

    I like the "text to colums" function in Excel. I use it to parse delimited data frequently. In this case there are two delimiters, spaces and commas, and I'm not sure if text to columns would grab all of that at once, but there is no coding involved.
  5. K

    Nested junction tables

    Yes, of course, sorry. Let me give it another shot. I have customers (groups in this sense, not individuals) who have the same parent company, but they are unique customers who invoice seperately, different contacts, basically different customers. Each customer has its own locations...
  6. K

    Nested junction tables

    I'm at a place in my design where I don't want to go further without advice for fear of really making a mess.:o I have Products, Customers, Customer Locations, and Customer Models that can have any number of combinations. I've joined what I think makes sense at the lowest level, customers with...
Back
Top Bottom