I have brought an app from 16.1 to 17.0b1 (also applies to prior alpha's).

THe following view works fine in embedded files but the moment I convert them to MSSQL Express 2008 standard files some child fields save with blank values.

I hinted at this in another post but needed to research it further.

DD Structure

Bank Account (Grandfather)
Primary index:
  1. Record Type 2 Ascii
  2. Bank code 9 Ascii
Transaction Header (Father)
Primary index:
  1. Record Type 2 Ascii
  2. Bank code 9 Ascii
  3. Transaction Type 3 Ascii
  4. Reference No 8 Ascii
Transaction Line (Child)
Primary index:
  1. Record Type 2 Ascii
  2. Bank code 9 Ascii
  3. Transaction Type 3 Ascii
  4. Reference No 8 Ascii
  5. Line No numeric 10.0
There are physical relationships between the obvious parent child links.
There are also DD Relationships on the same fields and pbUseDDRelates set to true in each dd class.
The Transaction header has Allow_Foreign_New_Save_State set to true.

There are constraints between:
Child & Father
Father and Grandfather

In the embedded database all parent fields permeate down to the child. - Perfect.
In SQL standard database
Fields 1 and 2 of the Transaction Header (Father) do not save down.
Yet interesting the same fields are saved to the child file perfectly.

The work around a found was to add the two blank fields to the father
Field defaults procedure and setting them to the grandfather values.

I have done a bit of debugging and the dd attach seems to populate correctly.
I have (sort of) concluded there is a difference in the saving process between SQL and embedded saves.

I thought i would do a quick revamp of the order entry orders view to make the customer into the grandfather with similar contraint levels and that did appear to work in SQL standard tables.
So I am a little puzzled.

It appears to me there is a difference in the save process between embedded and SQL standard tables.