Sharon

Yes! That could work. Thank you! It's even better than a concatenated list since it won't be so long. Great

I've attached my graph. The two tables are Locus and Feature. As you ca see, Locus is a much more elaborated entity. Also, the naming (the pk) of the records in them is different. In the Locus table I have a field that should hold a name of either a Locus or a Feature in the same area.

Thank for the responds. Well, the "moms and dads" naming was just for the sake of simplifying. In reality, the tables have very little in common. They represent two completely different entities and it's just this one incident where it would be very handy if I can list them in one list. LaRetta, I would love to hear more about the techniques you've mentioned...

Hello, I have two tables, both have a field "name". Let's call them the "dads" table and the "moms" table. In a third table (call it the "children" table) I want to have a field ("parent") where the user can choose a name using a drop down. The values in the dropdown should be all available names of dads and moms. I cannot find a way to concatenate the lists. I can build a concatenated list in a calculated field but I cannot find a way to use that list in a dropdown. Is there a solution?

Ok. I realize my mistake now. I've used the value list not for a simple field but for adding records in a portal that shows lines of a joining table. I understand now that the context of the portal is not the context of the layout it appear in, but rather the context of the joining table. I solved it with another instance of a table and it seems to work fine. Thank you very much for your time and answers

Thank you for your reply. I will use meaningful names in the future, sorry. My first thought was exactly what you describe (this is why I thought it was simple), but it didn't work. I've tried it again and realized my situation is more complicated. While it works perfectly in a simple layout of C (I'll stick to these names for now), I'm using a script that opens a new window as a card for creating a new record in C, and the user should choose the value from the list there. I don't understand why it works in the simple layout but not the card. Any idea?

Hi, I'm trying something that seems very simple, but I can't make it work for some reason. I've tried all sorts of joining tables etc. I have three tables: A, B, and C. Table A is the parent of both B and C. (so there is no actual relation between B and C, but there are records in B and C with a common A father). I want to add a field to C that will store a field's value from B. For that, I want to create a value list of values from B for the user to choose from. However, I do not want to show every possible value from B, only those that share a common father in A with the relevant record of C. Is there a simple solution for that? Thank you