I think you may be having a problem completely different to the one I was having. With the whole Web "loop", whenever you make a change to the data you need to save it to a session variable so that it does not get lost when a postback (not sure if that is the right term) occurs. In my case I was not doing this.

>I'm not sure what this means. I'm saving the child object in the same function and it's not saving for me (well it IS saving, but the new children don't get their foreign key assigned properly). Kevin sent me some new code to try, but I haven't gotten around to it yet as I've worked around it by explicitly forcing the FK into the child and saving it.
>
>Eric
>
>>Got It!!!!
>>
>>I wasn't saving the dataset in the session so it was disappearing before it saved.