<<
I only said that I have never constructed an application built around them. Rather than pointing out my alleged lack of experience, perhaps you could add value to the debate by giving an example that could be used often enough to move the practice from the 'rare' category?
<<

Erik, you really have a chip on your shoulder that you need to get rid of. The fact is it all goes to credibility. On one hand, you say that the need to do something is rare. Yet, you dont have the requisite experience to say whether it is a rare thing or not. I understand that you don't like me bringing up the experience issue. However, you brought it into the fold by a previous comment. I merely responded to it.

I will give you the same treatment as I have given others. When you don't have the experience that would otherwise be required to render an authoritative opinion, you should couch it as such. This way, the reader is properly informed.

The fact is, I have stored procs all over the place that return 2, 3, and one that returns 4 output parameters. Depending on how the proc is called, any number of them may or may not have values in them. I have alot of experience. And in my experience, it is not so rare of an occurance. Much of it is a style issue. Some people will build temp tables and stuff values into the temp table and return the table as a result set. To me, that is too much effort. T SQL allows you to return a value directly to a variable.

So with that said ERik, next time, don't let your lack of experience substract value from the debate by rendering an opinion that has little or no value.

Look, if you want to say that an occurance should be rare - back that assertion up. If it is just your opinion, then give the reader something that would give a reader reason why to take your opinion seriously.

I remember once I got the big smack down from Jeff Winchell about 6 years ago. I guessed at an answer. When Jeff asked if I had ever done the task before - I said no. Well needless to say, I got dressed down on CIS. From my perspective, Jeff did me one of the biggest favors anybody has ever done for me. And again, I will thank him for it.

If you don't want your experience to be a topic of debate - the lack of it or otherwise -don't make an issue of it. And, as an MVP, I hold you to a higher standard. You may not like that. Then again, it is my standard - it is not here for you to like...

< JVP >



<<
The ease of tranlation is a good point. Having used ADO in both VFP and VB, however, I have yet to have a need to do this. But that's not to say somebody else doesn't.
<<

Not viewing things soley in the context of what *you* have the need for is the key. I am glad you recognize this.

I see yet again, you agree that the points I raised have merit and are good. I guess that clears the issue up....

< JVP >