Hi, Neil!

>>
B) Enclose each BO (Invoice and Invoice Lines) in a MM event object, as suggested by Jay van Santen higher in this thread.
<<

This is my favourite choice (by architectural reasons) - but I don't have practical experience <s> (I started last month working with MMF)!


>>
Please correct me on this if I'm wrong, but I'm assuming that we'd have to use SQL Passthrough to make sure both cursors are updated correctly, or rolled back if there's an error.
<<

Please take notice of dealing with connections: If You want to use *one* backend transaction for updating *two* cursors, you have to use the same connection for both cursors (backend transactions are connection-bound!!!!) and you have to switch off automatic transactions by using SQLSETPROP( "Transactions", 2 ).

BTW: May be there is an corresponding feature in MMF - in this case Kevin will jumping in <vbg>!