Can you explain why you are using "15 separate fields"? This sounds like a case where you should have 1 field from up to 15 related records. Such a structure will greatly simplify getting the corresponding name fields from a related table to show the names corresponding with the selected contactID.
Without that, you'll need either to use pop-up menus instead of drop down lists or to define 15 different relationships to 15 different occurrences of your contacts table.
Thanks for your reply. This is a 'port' from MS Access, where it was possible to load data and fill a field through a list field. Here, the list field is limited, so, it becomes quite akwared - ie your suggestion above to define 15 different Conacts relationships, one for each field - makes for a VERY cluttered schema.
I guess my cleanest alternative to is to strip out the fields into a seperate table - say, called 'Roles' where Contacts and Company are connected in a many to many type of set-up - is that possible?
Thanks again for the reply
Creating 15 different contacts relationships is not what Phil suggested. The opposite in fact.
Another option is to use calculation fields with ExecuteSQL functions if you are using FileMaker 12, but I'd take a careful look at those "15 fields" first.