>>If this is not the case and you want to go with one view, then you could call the NextID function explicitly when you add a new record to your view. Or it could be the default value at the view level instead of at the table level. When you add the record to the view, the default value function will kick in. Then you only have to do a little pre-processing to retrieve that value from the PK field and populate the FK fields in the same view.
>>
>>The default value won't (or shouldn't) fire for the table because the value is already specified.
>
>Default value at the View level is the perfect solution. I thought it was possible but couldn't figure out how to set a Default Value rule on the View visually. Can it be done or can you only do it programatically?
It must be done programatically. It can be done with DBSETPROP() unlike a table field's default.
Insanity: Doing the same thing over and over and expecting different results.