Showing related record from existing table to new created table

[Blythist]

I am having some difficulties with relationships in the FM Pro 11.

Currently, I have imported excel from online registration form into Table A. (with about 180 records in it).

I need to create the mailing list and I do not want to add fields into the big table, but to create separate table B, where i can use related records from Table A and add 'subscriberID' and 'active' fields in the Table B.

I have set up the relationship between both tables of the fields 'firstname', 'surname' and 'emailaddress' but the new table B doesnt show any records from Table A.

I suspect that scripting is needed to ensure the records is shown in the new table without duplicating, (in case an subscriber wish to update their email address, it will be updated in both Table A and Table B simultaneously.

FYI - I recently obtained the FileMaker at workplace. So i am sort of new to it.

Any help will be much appreciated.

[Vaughan]

I need to create the mailing list and I do not want to add fields into the big table, but to create separate table B, where i can use related records from Table A and add 'subscriberID' and 'active' fields in the Table B.

Why not just add the fields and make life easy? Scripting is not necessarily needed: if the relationship has "allow creation of related records" selected then the related records will be created the moment an entry is made in one of the related fields.

However, all of this is a lot more work than just adding the fields to the big table.

I just realised that you'll only be able to add a related table if the current big table already has a field that can be used as a primary key: it needs to be non-empty, unique, and invariant. A name field will not do. An e-mail address field will not do. If there is no suitable field you'll need to add one; then you might as well add the other fields and forget the related table altogether.

[Blythist]

Why not just add the fields and make life easy? Scripting is not necessarily needed: if the relationship has "allow creation of related records" selected then the related records will be created the moment an entry is made in one of the related fields.

However, all of this is a lot more work than just adding the fields to the big table.

I just realised that you'll only be able to add a related table if the current big table already has a field that can be used as a primary key: it needs to be non-empty, unique, and invariant. A name field will not do. An e-mail address field will not do. If there is no suitable field you'll need to add one; then you might as well add the other fields and forget the related table altogether.

Thank you for your clarification of using unique ID, I current have registration ID which it is unique to each registrations.

Hmmm, but eventually I will add more tables, to organise invoices, assigning the job to specific person, etc... I am not sure if one table would be sufficient?

Perhaps I should explain more clearly, we run community classes, the people who would like to attend the course, they register online. I can export the registration into csv or excel, then import into FM.

Some people may register more than 1 course, and in that case, the email list would be duplicated. SO that's the reason I am trying to make another related table, using email as unique id to ensure it is not duplicated, and will update the course list's email if the person's email changes, so i can send the certificate via pdf directly to specific class, etc.