It seems this may not be a robust as I’d hoped.
- I have set up project and task tables.
- I would like many tasks to one project.
- I went to tasks table, created link to projects with “allow linking to multiple records” disabled.
This works great for assigning a task to a project.
If I now go to the projects table I can still assign an already assigned task to a different project and this then carries back through to ‘pollute’ the task can only be assigned to one project constraint I set up.
Seems the many to one is not truly in the database but just in the selection phase of the app.
Worst case I could hide the link field in the Projects table and replace it with a lookup showing the same thing - this will force users to initate the link in the tasks table where the front end entry is enforcing the one-to-many while still allowing view of tasks.
Is this just a limitation or is there a way I can work around this?