I did a quick database for what i want to achieve above, made a table called Reptiles with the above fields, and then duplicated that occurence for the sire and another for the dame, i related the fields like so:
Reptiles::ReptileSire -- = -- Reptiles Occurence Sire::ReptileTagCode
Reptiles::ReptileDame -- = -- Reptiles Occurence Dame::ReptileTagCode
it displayed the sire and dames info properly, and i can just repeat my steps buy creating occurences for for the sires and dames up to 5 generations, but thats gonna be alot of table occurences and im wondering if this is gonna be riddled with errors later on or if it is sloppy coding, maybe there is a better secure way of doing this?
Multiple table occurrences seem like the right approach to me.
I have to get back into this topic, my genealogy tree works great, and now im looking to show all the sibblings of each reptile in a portal, meaning all reptiles in the database who share the same mother and father.
my family tree is done just as said above, with multiple table occurences of the Reptiles table. I created another table occurence called "Reptile Sibblings" and added a text field called "ReptileSibbling" and related Reptiles_Sibblings::ReptileSibbling --- = --- Reptiles::Reptile_TagCode
ReptileTagCode is a a unique identifier that breeders give their reptile, its always unique and a required field in the database.
I can see my relationship is setup wrong, i also tried relating to the Reptiles::ReptileID, but still no luck. the sad part is years ago i actually had it working in my old database similar to this that i developed and lost in my hard drive crash, but i cant for the life of me figure out how i did somethings before..
oh nevermind i figured it out, just related the Parent fields between the two occurences.