I am currently struggling to get data flowing correctly. The end goal is to send data from an installation table to a verification table (basic site information and services to be verified). The verification table will use the data from the installation table and add verification details and return the data to the installation table.I currently have three tables to accomplish this, the installation table, verification table and a bridge table. The current relationships are: The installation is the parent for the verification table, the verification table is the parent for the bridge table and the bridge is a parent for the installation table. My thinking on these relationships is the installation table sends data to the verification, the verification table sends the verification data to the installation table via the bridge.I can get data to the verification table and to the bridge, but not back to the installation table. I have two questions. First, is this logic sound? The second question is a little more cloudy. Another team member added a relationship with the verification table being parent for the installation table thinking we do not need the bridge table. Would this relationship in any way prevent the data flow from the bridge to the master or would if cause any other issues.There is one additional problem. The key field in the Installation table may not exist in the verification. The key in the installation table is the project number, but not everything being verified will be associated with a project number.I apologize for the lengthy post, I wanted to provide as much information as possible.------------------------------Paul------------------------------

Can you provide a more specific use case? I am not quite sure what the three tables are actually doing as it sounds like you are trying to automate some process vs just store data in a table.------------------------------Ivan Weiss------------------------------

In a nutshell, there are two teams that work somewhat in tangent with each other. We have a group focused on installation of products/software and another team working with verifying the services are installed and functioning. However, the verification team also works with repair and troubleshooting issues that are unrelated to installs.The installation team has a form showing the upcoming installations. One section of the form needs to include feedback from the verification team showing that the services are in fact installed, it there were any issues, details and notes about any issues. The verification team needs to see the services that were ordered from the installation table and update their form in the verification table. The results of that need to update the fields in the installation table.I found part of my problem a little while ago. I have my relationships wrong. I need to have the bridge table be the child of the Installation and the verification tables. What I am not sure is how to get the info to the verification and installation tables from the bridge table.------------------------------Paul------------------------------

Paul, personally I think you might have a design issue.... At first glance anyway....The tables represent the noun's in your use statement, or the objects you need to store information about... I see tables needed for: Products/Software Installation Service Calls Customers Technicians In this design any particular product can have many installations or any product can have many service calls.Each customer can have many installations or many service callsEach technician can have many installations ir many service calls (if you send multiple techs you need a join table here)By doing that I think you move the data to the appropriate places....------------------------------Ivan Weiss------------------------------

I agree there are design issues and plan to resolve them as time permits. At the moment we have a tight deadline. Is there a way to get the data from the bridge table to the installation and verification tables as they are currently configured?------------------------------Paul Peterson------------------------------

Can you map out the relationships for me? Mark showed me a good method.Table 1 < Table 2Table 1 has many Table 2. Just helps show which way the data can flow.And/or if it is simple post a screenshot of your app diagram.------------------------------Ivan Weiss------------------------------

Help needed with Many to Many relationship

IvanWeiss
Qrew Captain
5 years ago
Can you provide a more specific use case? I am not quite sure what the three tables are actually doing as it sounds like you are trying to automate some process vs just store data in a table.

------------------------------
Ivan Weiss
------------------------------
- PaulPeterson
  Qrew Member
  5 years ago
  In a nutshell, there are two teams that work somewhat in tangent with each other. We have a group focused on installation of products/software and another team working with verifying the services are installed and functioning. However, the verification team also works with repair and troubleshooting issues that are unrelated to installs.
  
  The installation team has a form showing the upcoming installations. One section of the form needs to include feedback from the verification team showing that the services are in fact installed, it there were any issues, details and notes about any issues.
  
  The verification team needs to see the services that were ordered from the installation table and update their form in the verification table. The results of that need to update the fields in the installation table.
  
  I found part of my problem a little while ago. I have my relationships wrong. I need to have the bridge table be the child of the Installation and the verification tables. What I am not sure is how to get the info to the verification and installation tables from the bridge table.
  
  ------------------------------
  Paul
  ------------------------------
  - IvanWeiss
    Qrew Captain
    5 years ago
    Paul, personally I think you might have a design issue.... At first glance anyway....
    
    The tables represent the noun's in your use statement, or the objects you need to store information about... I see tables needed for:
    
    Products/Software
    
    Installation
    
    Service Calls
    
    Customers
    
    Technicians
    
    In this design any particular product can have many installations or any product can have many service calls.
    Each customer can have many installations or many service calls
    Each technician can have many installations ir many service calls (if you send multiple techs you need a join table here)
    
    By doing that I think you move the data to the appropriate places....
    
    ------------------------------
    Ivan Weiss
    ------------------------------

Forum Discussion

Help needed with Many to Many relationship

Related Content

Cross App Relationships

Scheduling Formula needed

Database Expert Needed

How to Link Tables in a Complex Many-to-Many Relationship?

I need help creating a snapshot field in a unique parent-child relationship.