>>>
>On the backend, a component takes care of reading the message and traversing the recordset to make the inserts.
><<
>
>Explain this step to me. Tell me exactly how you accomplish this. If you are using the Update/UpdateBatch methods of the recordset, there is no need to "traverse" the recordset. If you are using some other means of updating, say taking the data from the shaped recordset and marshaling it a command object, then you have just made my point.
>

Right, to a command object. What I don't see is how it can be said that they don't work reliably.

>As far as MSMQ is concerned, I don't see that as being relevant to the issue.
>

I guess it's not. The point was that you only send one message to pass the data. Which is really about the shape recordset.

>Also, I would be interested in the metrics of your app.
>
>
>Also, please explain this statement:
>
><<
>You have a parent-child relationship that is all on the client side at the time the data is collected.
><<
>
>Is this new data? Or, is this existing data? Please clarify...
>

Yes, new data where all child records for the parent are available and collected at the same time.

>
>Thanks,
>
>< JVP >
>
>