Thank you very much BruceR for the example.
It gave me new insight how to design in Filemaker. Nevertheless, is solves half of my problem. It works fine as long as I always have a meeting record. If I create a Task from Tasks layout, it won't and shouldn't always have a meeting. Now I cannot assign it to someone. Choosing from Peoples Layout a person I would like to see all his/her tasks (created through meetings and separatelly). Now, if the meeting exist it works and if not I won't see those Tasks from Peoples layout.
Therefore I need a second join table between tasks and people for assigning tasks to someone and to see all tasks assigned to someone form Peoples layout. From that need I got my own initial idea of adding tasks relations also into the same join table (currently the table Meeting_People). This solution didn't work as I expected. Making a new Task from Task layout and assigning it to someone, filemaker looked for a first record that referred to that person and saved the relation into that record (that was initially a record for stating who took part of some meeting). Assigning next tasks to someone from Tasks layout were joined through a new record in Meeting_People table, so as I thought could have happened for the first one as well.
Now I know that I have to use not more that two way joins in Filemaker, do you think my understanding is relevant?
I attached my new solution here (relation for adding assignees to tasks), do you think my approach is now more Filemaker way?
Thank you in advance
Aman
TESSTMOD2.fmp12.zip