>>I think the business need for adding a parent and a child at the same time to the same cursor is probably much rarer. I've never had a need to do it.
>
>Erik - what about the case where a line item may have additional line item information in a one-to-one if it is a line item of a certain type?
>
>Example - I sell widgets, things, and doomahickeys - all separate inventory codes for my line items. doomahickey line items have extra information that the other two don't need. Only a small portion of my business is doomahickeys so it is bad-magic (not to mention denormalized) to just add extra fields and null them for other types. I need a one-to-one in a cursor and both updateable.
>
>Stuff like this happens all the time. Surprised you haven't seen it.
>
>thanks,

So, how do you differentiate between adding a new part that needs a doomahickey table entry and one that doesn't? If you're always adding a doomahickey table entry, why not just use extra fields on the part table?