Discussions

Expand all | Collapse all

Updating App - Suggestions on table/form design best practice?

  • 1.  Updating App - Suggestions on table/form design best practice?

     
    Posted 12 days ago
    I am updating an app I previously created and trying to implement some better "best practices".
    One of the areas I am focusing on is better use of intermediate tables, aka Many-to-Many.

    My previous app had a part of it set up as follows:
    • Tables
      • Work Orders
      • Clients
      • Contacts
    • Relationships
      • Clients < Contacts
      • Clients < Work Orders
      • Contacts < Work Orders (x8)
    In my contacts table, there are several different types of contacts, e.g. VP, AVP, Supervisor, Manager, Specialist, etc.
    In the main Work Orders form, I have 8 drop downs, each stemming from one of the 8 Contacts<Work Orders relationships, and each representing one of the different contact types. Each dropdown is conditionally reliant upon the client selected in the Work Orders form.

    I was curious if there was a better way to do this, perhaps using a M:M relationship, maybe a table between Contacts and Work Orders, .... however thinking through this, I would still need to have 8 dropdowns, one for each contact type .... would it really add any benefit using a M:M table in that scenario, or should I leave it as I previously had it ????

    Thanks for your input and suggestions ... I appreciate them ...

    ------------------------------
    Andrew
    ------------------------------


  • 2.  RE: Updating App - Suggestions on table/form design best practice?

    Posted 12 days ago
    When you select a contact #1 (of the 8) for a work order, are they being slotted into a named relationship like Key Contact, or Building Manager?

    If they are, then  if you go to a Many to Many Relationship, you would need to label the child records as they are being created as to the Role that Contact plays in the Work Order.

    The factor to consider is sending automated emails. The brute force method you have in place now with eight relationships is in fact quite convenient if you want to send emails to update the contacts as the work order status changes. ​

    ------------------------------
    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach
    http://QuickBaseCoach.com
    mark.shnier@gmail.com
    ------------------------------



  • 3.  RE: Updating App - Suggestions on table/form design best practice?

     
    Posted 12 days ago
    Mark, thanks for the response.

    Yes, there are 8 slots in the Work order, each one is identified as representing one of the 8 different contact types.

    I first select my client, then I can click the dropdown which represents the VP, and it will only show me contacts from that client that have a contact type of VP. The same goes for the other 7 contact types, only showing me those specific contacts that are of that type and for that client.

    As far as sending emails, I am not too concerned about that issue as the contacts themselves would not be receiving any emails.

    Although I do like the simplicity which the brute force way of doing it allots me ... any pros to doing a m:m vs. this brute force method?

    Thanks again!

    ------------------------------
    Andrew
    ------------------------------



  • 4.  RE: Updating App - Suggestions on table/form design best practice?

    Posted 12 days ago
    If it ain't broke, don't fix it.

    ------------------------------
    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach
    http://QuickBaseCoach.com
    mark.shnier@gmail.com
    ------------------------------



  • 5.  RE: Updating App - Suggestions on table/form design best practice?

     
    Posted 11 days ago
    Hahahah, great advice. Thanks Mark!

    ------------------------------
    Andrew
    ------------------------------