Hi William,  I assume you are only creating one job that requires many default values already set in the client table.  
The best way I believe is to have a cross-reference table.  ClientT - CrossreferenceT - JobsT.  Mind you I would have a separate table for the client Defaults as well unless it is a very static unchanging set of defaults.

In CrossreferenceT you have ClientId & JobId & DefaultsId

Example

ClientIDJobIDDefaultId
111
113
114
115
121
123
131
135
241
243
244

That's how I'd approach it.  I'm sure there are other ways.

Sorry above didn't put in all the tabs

C-J-D so the above 1st record of 111 is 1-1-1 and C is Client, J is Job and D is Default

Thank you!

Remember, while it's possible to pass information from one table to another, the only time you really have to do this is if you care about what that information was at the time. For example, if you're talking about a customer and an order, then you want to pass the customer address to the order table because you want to know where the order was shipped at that time. However, other information where you don't care about the timing can simply be looked up from the parent table. For example, with the contacts table, you wouldn't necessarily pass the customer's phone number to it because you can always go back to the customer record to look up their phone number, their current phone number. So, unless you've cared about the phone number that you actually called at the time, which might be important for a call center but generally isn't something that you need to copy between multiple tables. I talk about this concept in detail in the Extended Cut for the invoicing video.