Actually, FM is pretty good at doing what you want with a minimum amount of work. First set up the fields for the two tables the way you are describing them. Then use the Filemaker import tool (File->Import) to import the data into your new tables. If the old database is a filemaker database you can do it directly. If some other format you can export it to a format filemaker recognizes and import it.
Ok Between table1 and table2 I setup a relationship before importing:
descriptions_pk = descriptions_fk
When I imported all my titles I got 3900 titles imported.
Title -> Title
So now I looked at my title layout and I have 3900 titles and each one of them the has a blank value for the descriptions_fk, makes sense I think. Then I go to my descriptions layout and I import my eng_descriptions and all those values increment to 3900. I went to my title layout and added the field for eng_desc from my related table, but none show up, because for some reason the table isn't relating when I import.
I must be missing something on matching or updating when I import I'm assuming. My serial # increments in import and when importing I ask it to update the serial # when importing.
I'm guessing you've got the usual problem in moving a flat/unrelated db into a multi-table related field. That being that the flat db had all the data in one "table" and didnt need anything to associate the two parts of the table. When you import the data into the two new tables you have to provide the key that relates the two new tables. The update serial numbers option doesnt do it because it creates a serial number for the table/record it is creating and nothing to relate it to the other table and it's associated/related record.
You've got the right idea in setting up the key fields. Now you just need something to use during the import that provides the "key". If you can modify the old database, add a single key field to it, and populate it with unique numbers. Now when you re-import the data one table will have half the data and the key field as a foreign key. the other table will have have the data and the key field as a primary key. That's how the relationship get's established.
If you can't modify the old database to add a key field, you can import the whole table into a single filemaker table, add the key field there using the "update serial numbers option" when you import. Then reimport that table into your two new tables as described above.