Forum Discussion
RyanStanford1
7 years agoQrew Captain
I think I figured it out somewhat... I think the reason I was attempting to make the [Airport Name] it's own field and update the lookup field [Airport - Name] is because when I try to just use the reference proxy field, it's using the standard record picker, instead of a drop down, even with me having it set to show as a drop down.
- ChrisChris7 years agoQrew Assistant CaptainOkay, so in Requests table, Airport Name is piped in via the relation, it s not its own field.
- RyanStanford17 years agoQrew CaptainAt the moment... I have both... Airport Name is its own field, but then there's Airport - Name which is piped in via the relation...
really what I'm looking for is one of these fields working as a drop down, and when that field is populated, the relation is populated. - ChrisChris7 years agoQrew Assistant CaptainDelete the Airport Name field that stands alone in the Requests table. Use only the Airport Name "Relationship". The proxy field [Airport Name] will serve as your drop down list. In the Requests table, open the Related Airport field properties. Set Airport Name as its proxy. Then you can use Airport Name as the drop down list.
- RyanStanford17 years agoQrew CaptainGot it! I think I've also been battling the fact that the limit of a drop down list is 1000 records... My Airports table is 5500.