I am new to Filemaker Pro and am attempting to design a genealogy database for my own use. In theory, each individual in the database is assigned their own record displaying birth, death and marriage details etc. Should the individual have children, I would then like a list of the children's names to be displayed with the user being able to select or click on a child in the list which would then display this individual's record.

Would it be better to use a portal or some kind of list/menu field for this. If using a portal, am I able to assign the 'go to record' script to each row (individual) in the portal or only the portal as a whole?

Thanks for your help.

Elle

I am new to Filemaker Pro and am attempting to design a genealogy database for my own use. In theory, each individual in the database is assigned their own record displaying birth, death and marriage details etc. Should the individual have children, I would then like a list of the children's names to be displayed with the user being able to select or click on a child in the list which would then display this individual's record.

Would it be better to use a portal or some kind of list/menu field for this. If using a portal, am I able to assign the 'go to record' script to each row (individual) in the portal or only the portal as a whole?

Thanks for your help.

Elle

I am new to Filemaker Pro and am attempting to design a genealogy database for my own use. In theory, each individual in the database is assigned their own record displaying birth, death and marriage details etc. Should the individual have children, I would then like a list of the children's names to be displayed with the user being able to select or click on a child in the list which would then display this individual's record.

Would it be better to use a portal or some kind of list/menu field for this. If using a portal, am I able to assign the 'go to record' script to each row (individual) in the portal or only the portal as a whole?

Thanks for your help.

Elle

Elle:

Welcome to the Forums.

You would use a portal. Genealogy is probably the simplest subject in which to apply a relational database, because the terminology used in relational design is "parent" and "child." Your "child" records would appear in a portal in your "parent" record, and you can put a button (Go To Related Record) in the portal row which will go to the related record. The relationship would be based on the unique identifier key of the "parent", such as a serial number, which need never be seen by the user...

-Stanley

Elle:

Welcome to the Forums.

You would use a portal. Genealogy is probably the simplest subject in which to apply a relational database, because the terminology used in relational design is "parent" and "child." Your "child" records would appear in a portal in your "parent" record, and you can put a button (Go To Related Record) in the portal row which will go to the related record. The relationship would be based on the unique identifier key of the "parent", such as a serial number, which need never be seen by the user...

-Stanley

Elle:

Welcome to the Forums.

You would use a portal. Genealogy is probably the simplest subject in which to apply a relational database, because the terminology used in relational design is "parent" and "child." Your "child" records would appear in a portal in your "parent" record, and you can put a button (Go To Related Record) in the portal row which will go to the related record. The relationship would be based on the unique identifier key of the "parent", such as a serial number, which need never be seen by the user...

-Stanley