Filemaker Pro 13, How to added duplicate related records to a related database with no duplicates without using a portal.

I have two Filemaker Pro 13 databases, one with no duplicates and the other with duplicates that are related to each other by a field called ITEM. I want to add a single field to the non duplicates file to contain some information in the duplicates file without using a portal. In the duplicates file there is a field called WHSE. How can I add all duplicate records to the single field in the non duplicates file. Hopefully this makes sense how I am explaining it.
John O'ConnorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will LovingPresident, Dedication Technologies, Inc.Commented:
If I understand you correctly, you are asking how to display in the non-duplicates file, all the values in the WHSE field for the related records but without using a portal to do so. If that's correct, then the simplest way to do that is to use the List() function (I'm assuming that there is a relationship between the non-dupes table and the duplicates table called "RelatedTable" using the field "ITEM" as the key field)

List( RelatedTable::WHSE )

This will give you a carriage-return delimited "List" of all the values. In general, any time you have a list of values separated by carriage returns in FileMaker, it's referred to as  "List" of values.

To display those values as a comma-separated text string you can use the Substitute() function on the list:

Substitute( List( RelatedTable::WHSE ) ; "¶" , ", " )

Something to keep in mind is that as your database grows it will be much easier to manage if you keep all your tables in one file. I would recommend importing which ever is the simplest table with the fewest scripts and layouts into the other file so you only have one file with multiple tables. It will take a little time but it will make life MUCH easier especially as things get more complex.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
John O'ConnorAuthor Commented:
Perfect, thank you for your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
FileMaker Pro

From novice to tech pro — start learning today.