1 of 1 people found this helpful
It makes sense as far as it goes--a lot of detail is missing, but you really need to break this down and tackle one issue at a time. The first question appears to be, (correct me if I misunderstood): You have exported data from some other system into two files and you want this data to be in two related tables of the same relationship. You have an account name field that matches entries in the two files of exported data. Is this correct?
If so, you can use import records to import this data into two tables of the same file. In Manage | Database, you can set up a relationship that links the records in the two tables by account name. Once the data is in place, you can work on your layouts and the portal you describe.
And working with your imported data to link by a unique ID that is not the account name is also likely to be a worthy improvement to make to your original design once you have your data imported--but you'll need to let us know if this is a one time export/import or if you will be importing new data from this source on a regular basis.
Thank you. This is very helpful. To answer your question... this will be a import that will happen again with more and new data.
Then you will need to keep your relationship that matches records by account name in place. But if possible, I would use this relationship only during the import process via scripting or auto-enter options that leave the newly imported data linked by an account ID that is generated from within FileMaker. This makes for a bit safer relationship for linking the data in your two tables. Basically, you use the name during or just after import to (create if new first) copy over the needed ID--which you then use throughout the rest of your database. This requires using two occurrences of the same table so that you can have a relationship that matches by account name and also one that matches by ID.