You have Projects, Teams, and People
Projects can have one Team?
Teams can have one Project?
Teams can have many People.
People can have one Team?
People can have one Project?
By the conventional wisdom, you need a Teams Table.
A well-designed database promotes consistent data entry and retrieval, and reduces the existence of duplicate data among the database tables. Relational database tables work together to ensure that the correct data is available when you need it. It’s a good idea to plan a database on paper first.
Follow these general steps to plan a database:
Relational Database Design 101 (part 1 of 3): Designing a Flat File Database
Relational Database Design 101 (part 2 of 3)
Relational Database Design 101 (part 3 of 3)
The White Paper for FMP Novices is useful -
thanks, for some reason I was avoiding a teams table. I've gotten pretty far without it... up until now that is.
You don't need the team table.
I just made a little test. I'll try and see if I can make a little screencast to demonstrate what I have done.
Allright, I think I found the solution to your problem. And I recorded it in a little screencast. You can see it here:
First I create the simple Conditional value list and then I add the twist :)
If you want to see the video in proper high resolution, then change the video resolution thingy in the bottom of the youtube video screen:
Thank You so much! Very elegant solution. If i went back to add a teams table, it would be such a headache, since my database has several more tables and multiples occurences. This works perfect for the simple selection that's needed.
I created a sample based on DaSaint idea. Using a droplist to select group and using a portal to display the team members. Incase you need to see the members on a report or all on the screen at once.
Sample file at the following link: