Is it possible for a value list to use values from fields in multiple tables? Or can you combine more than one value list into a single value list?
A use values from Field value list can only list values from a single occurrence of a single table. Well, technically, the second field could show data from a table occurrence related to the table occurrence used for the first field, but that won't produce the result that you want here.
If you describe your data and why you would need such a value list, we might be able to suggest a way to get what you need via other methods.
I have one "buyer database" that needs to pull data for a value list from two "seller databases". For multiple reasons, the seller databases cannot be combined at this time, but they have similar data. For instance each seller database has a "listing number" field and that is what I want to use to input the information into the buyer database which has relationships with both seller databases. They way I have it set up right now is to have the same field on the layout twice, but with different value lists and when you pick a value, obviously it shows up in both places, which is fine, but can be confusing, I suppose. So, I thought it would be better used if I could combine both those value lists into one. I'm not sure if this makes a lot of sense. Please let me know if you need more details. Thanks!!
You really need to combine this data, if not the full files--though the reasons for keeping them separate may not be as persuasive to me as they are to you.
You could, for example, import the data from these two tables into a unified table of just enough fields to support what you need to accomplish with this value list. Scripts might update such a table nightly or transaction by transaction throughout the course of the day.
As an example, one non FileMaker DB that I used to manage and develop for had a unified table of SKUs and descriptions that combined all products produced by and all materials purchased by the company (Purchased in order to manufacture product or purchased for outright resale). These items had very different purposes and very different purchase or manufacturing specifications, but those very different data items were put in related tables linked to this one unified table of all such items.
Retrieving data ...