>Is that a point, or a statement of fact? It is a fact that you do pass all the parameters back - regardless of whether the values changed or not. One point might be that scenario is not good. Another point might be that it does not matter.

I have no idea if there is a performance cost, I was only trying to clarify for Charlie what John was saying. It sounds like in the type of application that JR is involved in, extremely wide records are common, and a list of parameters 200 long might be a real, rather than perceived concern, especially if the client can edit several child records at once.

Like I mentioned to John in another message, I would like to see some comparisons before I would chalk this up to a disadvantage to Stored Procedures.