Forum Discussion
JamesTrory
8 years agoQrew Assistant Captain
Hmm, I'm not quite sure what you mean. Do you mean records that are shared between the two tables that can be used to link data?
So I'll explain the use case. It's long-winded but thorough :)
I work in a photo studio and we are using a database built in Quickbase to track images through the post-production process. All of the tables used in the database are regular tables, I can't convert them to connected tables (I wish I could, that would make this so much easier). And it would be waaaaaaay too much work to try and rebuild the entire database to accommodate connected tables. It's just not an option.
Each image is represented by its file name, or ShotID. At the end of every day I import an Excel sheet into a Quickbase table called Shots that creates new records for all of the day's new ShotID's.
Every morning I then have upload and download Excel reports that I also have to import into Quickbase. These reports match each ShotID with new rows of data that show things like when a ShotID was sent to the retouchers (To MRC), when it was returned from the retouchers (From MRC), when it was published (To OTMM) etc.
This import of upload/download data is the part I'm trying to automate using a connected table. I import the upload/download data into the connected table and it then needs to see the ShotID's and match them to the ShotID's in the regular table, Shots. This will then update the ShotID rows with the new data from the connected table.
Basically, the connected table is a connected version of the Shots table. So I think, to answer your question, the identifying information is ShotID. I need to create a relationship between the connected table and the Shots table that match ShotID's together. I have tried this, with ShotID being the master record and then telling it which other columns/fields to copy to Shots, but it doesn't work.
So I'll explain the use case. It's long-winded but thorough :)
I work in a photo studio and we are using a database built in Quickbase to track images through the post-production process. All of the tables used in the database are regular tables, I can't convert them to connected tables (I wish I could, that would make this so much easier). And it would be waaaaaaay too much work to try and rebuild the entire database to accommodate connected tables. It's just not an option.
Each image is represented by its file name, or ShotID. At the end of every day I import an Excel sheet into a Quickbase table called Shots that creates new records for all of the day's new ShotID's.
Every morning I then have upload and download Excel reports that I also have to import into Quickbase. These reports match each ShotID with new rows of data that show things like when a ShotID was sent to the retouchers (To MRC), when it was returned from the retouchers (From MRC), when it was published (To OTMM) etc.
This import of upload/download data is the part I'm trying to automate using a connected table. I import the upload/download data into the connected table and it then needs to see the ShotID's and match them to the ShotID's in the regular table, Shots. This will then update the ShotID rows with the new data from the connected table.
Basically, the connected table is a connected version of the Shots table. So I think, to answer your question, the identifying information is ShotID. I need to create a relationship between the connected table and the Shots table that match ShotID's together. I have tried this, with ShotID being the master record and then telling it which other columns/fields to copy to Shots, but it doesn't work.