Mike,

>Everything works except that when I add a new parent record, then add new child records without first saving the parent, I get constraint violations in the database. Is there a way I can force the parent record to be written to the db first? Adding new child records to an existing parent works great.

Rather than saving each child row as it's added, you can have a single Save button on the form that saves changes to the parent object. If you register the child business object with the parent business object (see the MM .NET Dev Guide topic "Establishing Business Object Relationships" for details), the parent saves first then the child object is automatically saved afterwards.

>Also, if there is something a little more elegant for setting default values for columns in the new row, I'd love to use it!

There is a better built-in MM .NET way to do this. Check out the MM .NET Dev Guide topic "Setting Default Values in New Rows".

Regards,