The simplest way is if you have a primary key to foreign key relationship defined between the tables (explicitly defined - in table relationships).
Then you can just create a parent form (main form) and a child form (subform). Access links up the records for you automatically (handles creating the values for the foreign key when you add records in the child form.
So, that's the easy way which I don't know if anyone ever uses properly.
You are complicating a little by wanting (or preferring) a combobox instead of using inbuilt MSAccess navigation and filtering. It should still work but you would have to roll your own navigation, which is not so easy. This link tells the ugly story (ugly unless you know what you are doing, anyway):
http://www.allenbrowne.com/ser-03.html
There might be other ways, I don't know really.
Finally, you can just add sql or code to your form so that when a record is saved you get the parent ID and add it to records in the child table. That's not hard - you just intercept the Before_Save event and do the dirty work. If you have the information you need on a form or subform then it won't be hard to get that data just before saving, and update the record accordingly. Basically - you do have the information since it will be based on the combobox selection, so just go ahead and use that value.
As a an alternative, you can sort of do the same thing only when you save the Profile_Table records - each time you add a record, just intercept the save event and use it to populate the Time_Form table in advance. But you have to be sure you have control of the insertions - if you are doing this in a form, for instance, then that should be the only way a record is inserted. Then you don't need to worry about it later - records are already there. Or for the best of both worlds (worst of both worlds?) you can do both - insert Time_Form records at the earliest possible moment, and also check if they are there when you first use them, and insert them if for some reason they are not present.