Let's see if I have this straight...
Your relaitonships are: Investor-----<Investment>-------Deal
Your value list is to list all "deals" for the current investor record.
Is this for a field defined in Investor or in an Investment field that's part of a portal to the Investment table?
Assuming that this is for a field in Investor,
You can set up a conditional value list that lists fields from Deal, Include only related values starting from Investor and there will be no need to add a field for the Deal name in the investments table.
Thanks for responding. You are correct in what I want to do. While I am on the Investor form, I want to have a drop down that shows the deals the investor is involved in. When the user selects a deal, the system will open a details form about that deal.
> You can set up a conditional value list that lists fields from Deal, Include only related values starting from Investor
This is exactly what I want to do, but I am not sure how to do it because there is no direct relationship between Investor and Deals. Will Filemaker "walk" the relationship tree automatically? Any explanations about how to do this would be appreciated.
I also want to have a portal showing a line with all of the deals an investor is involved in. One of the things I want to show in the portal is the name of the deal. Do all fields in a portal have to come from the same table? Normally I would have a query that had all the fields I want to show. Can the source of a Portal be a query, or only a table. Is this even possible to do?
Thanks again for the help, Michael
In Manage|Database|Relationships If you link the tables as Phil states you can put the related Deal::Name Field in the portal and it will evaluate it based on the portal rows DealID
FM uses static Relationships instead of Queries. It uses Table Occurances to create multiple relationships with the same table.R
Thanks very much for the info. I will try that out.
I still have a lot to learn, but I am certainly enjoying the tool.
Yes, FileMaker traverses the table occurrences and their relationships as specified by you in Manage | Database | Relationships. This can create confusing results sometimes when you get more than two occurrences away from your starting point, but it does work if you carefully analyze how each relationship along the way affects the end result.