Thanks for including that. I installed it into my test db and have been studying the tables. But this is one of the things that has confused me in the past. And I know it's my lack of knowledge of SQL that's killing me. And I've learned that there are many ways to do one thing and everyone uses different methods.
In your relational table model_engine, there are no FK. Your index is primary key with both fields being the primary key.
And I don't see any FKs anywhere. So that confuses me because I've seen this done in other examples too. But everything I read says you use FK to relate to the other tables.
Also, just curious. When I look at the tables, I don't get the "Relational View" link next to the "Print View". It's missing in all your tables, so that tells me your tables are most likely setup differently than my practice tables. So what am I doing wrong?
I stripped out all the extras from my practice db using the Male, Female, Breeding Schedule scenario. I created 3 tables
Table 1 is for the Male dogs.
Table 2 is for the Female dogs.
Both have an id, name, comments field.
On the web site, there is a page for the Male dogs and a second page for the Female dogs. Each page has repeating regions showing all the records for each. (There is also a thumbnail photo in each record).
I've done several of these repeating regions without any issues. And they all include back-end admins for CRUD.
Now, on to Table 3. The web site will have a 3rd page. Just like the other two pages, it will have repeating regions but these records will show breeding pairs each year. So 1 Male, and 1 Female form the other pages. And include their photos without having to upload them again.
This is where I get lost. On the one hand, this could just be another basic flat table with it's own CRUD pages. And I'm starting to think that may be the way I have to go for now. But I don't want to give up on this because future additions will make a flat table unpractical.
Please take a look at the print views I included to see what I have, if you don't mind. I know that some of this is working based on my tests. But I can not figure out the php for it. And DA Wizard does not address the relation of multiple tables. (Please see my PHP questions below images).
PHP ??? On the Breeding Schedule page, do I create all three record sets? rsMales, rsFemales, rsBreedingSchedule? Or do I create one record set using some kind of join?
What I want is for all records to show (repeat) down the page with each record showing the information from tblMales, tblFemales and then tblBreedingSchedule. I know this is elementary stuff for most, but I'm blocking something out here.