Unless the stored procedure is required, you can do this with a disconnected, batch-updatable recordset. You can obtain an empty recordset from SQL, have it updated at the client and send it back through the COM object with the recordset's UpdateBatch method. No stored procedure required.

See the thread "Using Disconnected Recordsets" from today for some code on how to open the recordset. HTH

>Hi gang,
>
>This one's important, and I need a solution *fast*.
>
>I have an ADO recordset, containing new data. I need to *pass* this recordset, from a VFP COM object I've created, to a SQL stored procedure, which will INSERT these rows into a single SQL table.
>
>How the (expletive deleted) do I pass this recordset so that the stored procedure can see it, recognize that it's an ADO recordset, and insert the rows? Or, alternately, should I maybe spin through the recordset and build an array to pass instead of the recordset -- but then, doesn't COMARRAY() get its ugly head into the mix?
>
>Using remote views or SPT is not an option, BTW (it's a LONG story, don't ask)(g)
>
>(Aside: I'll also be sending a different recordset to UPDATE rows, but I think if I can get the INSERT, I can figure out the UPDATE part.)
>
>*ANY* help is -greatly- appreciated, since I'm under the gun on this one.
>
>TIA,