>>>>>>Coincidentally, I'm having the exact same problem but only when trying to save new children. Existing ones save fine. The problem seems to be that the foreign key is not populating (a record does get saved, just with no foreign key). Is the syntax right, in that we just have to name the field or is there more needed?
>>>>>>
>>>>>>I've run through the debugger and get down the SaveChildObjects() and PopulateForeignKeyField() and the value that it's trying to save is zero, rather than the parent object's primary key value.
>>>>>>
>>>>>>Eric
>>>>>
>>>>>Hmm, I seem to remember a similar post awhile back. I wonder if there is some combination that causes that problem and Kevin had chimed in. Might should do a search here in this forum to see if that message is the same issue.
>>>>>Tim
>>>>
>>>>I've done some stepping through the code and it attempts to save the child in this code:
>>>>
>>>>

ChildResult = ChildBizObj.SaveEntityList();

>>>>
>>>>and then here:
>>>>
>>>>

public override mmSaveDataResult SaveEntityList()
>>>>{
>>>>	return this.SaveEntityList(this.EntityList);
>>>>}

>>>>
>>>>this.EntityList == null
>>>>
>>>>How could that be?
>>>
>>>Can you give me everything in your save method so I can see how the data is getting back in the business objects? You could just send me via email the code behind of the page so I can see how the data is being handled all the way from retrieval to save. I suspect there is an order issue.
>>>Tim
>>
>>Hi Tim,
>>
>>did you ever find out anything with this problem?
>
>
>Got It!!!!
>
>I wasn't saving the dataset in the session so it was disappearing before it saved.

Glad to hear you figured it out Frank,
Tim