You have to relate the primary key and foreign key fields in the relationship graph.
In the relationship you will see the check box that allows creation of related records via the relationship.
i\If the create is turned on in Daily from Clients then, from a layout based on client, you can create related Daily records via portal and the foreign key will autopopulate.
client and Daily must be related via PKClient, unique key in clients, and FKClient, in Daily.
You have 2 options, then:
1) The one from coherentkris (allow creation of related records), or
2) A script to which you pass the PKClient as a parameter, it goes to a layout based upon the Daily table, does a new record and glues the parameter into FKClient via set field (+ Commit).
I always found 1) misleading, because you see an empty line in a related portal and many people call and ask "what's that empty record for ?" and I got fed up with that...
3) Create the record through a relationship. This requires a relationship for creating records, but in most cases this ended up being the most efficient ( for development, user experience, and performance ). Magic Key, part 1 | FileMakerHacks - this article explains how it works. It's a little detailed, because Kevin was addressing something specific. But he explains how to create the record.
Also for # 1...this is one way to address the blank portal row issue: Creating New Records in a Portal With a Twist.
slooowly, Joshua, sloooowly... he's a Filemaker virgin
lol...True. But it's there. There are a number of things I wish I had been told as I was learning...while I couldn't use it on day 10, it would have been handy to know on day 25 when I was trying to figure out a sample file someone provided to me.
Thanks guys, appreciate the guidance. I've got it associating records now and works great. Just getting my head around the TABs idea opposed to forms to support all the different ares of data input.