>The trouble comes when a user creates a new record at the parent level. Consider this scenario:
>1. User creates new parent record
>2. User adds a single child record to new, unsaved parent.
>3. User adds grandchild records(s) to the new, unsaved child
>4. User attempts to add a second child record.
>
>BANG! What happens to the grandchild records? You can't save them because they'll be orphaned (or would that be grand-orphaned?)


Use Table Buffering on the child and grandchild. Cascade your save so the it saves from parent to child to grandchild... I would even wrap the table updates into a transaction.

BOb