I wonder whether I have done this data-saving mentioned above correctly.
Current working set-up:
- There is a central db where all tables are linked to. This is done by having as many fields in the central db as there are other tables each with their datatypes as the central db all linked via the trial short name, and vice versa, so there is a link both ways. So the central db saves the short name, and all tables pull from it. (All this is working fine across the app).
New version management table introduced now:
- On this amendment page I have created another table (called version management, formerly amendments). Just like any other table in the app this is modelled in the same arrangement as above. It has its short name field linking to the central db and then central db linking back to the version management each with the datatypes of the opposite db saved to create the relationship.
Now, when I go into the app tab and open up the record of one of the sub-tables I am testing this on, I don’t see the small ‘change search field’ under the field to indicate the link. I feel I need to be linking directly with the VM table above to make this work?
This is my workflow at the moment:
Do I need to link directly from my sub-table to the VM table, or can I go through the central table to the VM table, where this link already exists - and still have fields in my sub-tables populate based on data stored in the VM table (which is the objective here)?