John..

What you refer to is hearsay - which is not necessarity an unacceptable thing. Ultimately, it all goes to credibility. While at times I have been perceived as being inflamatory, from a technical standpoint - I have been credible, at least I have been told this..< bg >...

As far as the argument comment is concerned, that would matter if I was putting it forth as has argument in it of itself. The fact is, I am not. Rather, I am bringing it up as an example that is counter to the example of checking each parameter to see if the value changed before passing it back to the server.

As for the only guage of usefulness is in knocking down the alternative, I don't see the merit in that at all. My point is that you don't have to check the parameters for thier respective changed status.

My point can be further clarified that in the end, the same amount of work occurs. You can spin through the parameters on the client, and only send what has changed in a client-side rendered SQL Statement. In this case, you have the overhead of checking parameters and building a SQL String.

Or, you can use an efficient object - such as the Command Object and work with a collection of parameters. Not string concatenation here. No type checking involved as is the case when you concatenate strings. No string passing. Rather, I am passing an object. I suppose I could pass XML as well. XML would be a better alternative to a concatenated string.

For sure, the blink of an eye comment was not an argument. Rather, it was just an example. The aforementioned....that was the argument. As for whether it is useful to you or not, that is your call as it is completely subjective. I think to many, it is useful...


< JVP >

>That your SP app is "as fast as the blink of an eye" is not a useful argument unless you can show the alternative is not.
>
>I am reminded of the defendant who was told in court "there are 5 witnesses who saw you do it." The defendant replied "So what? I can call 10 witnesses who didn't see me do it."
>
>Regards
>
>JR