Kevin,

Two things... If you are this indecisive in what you want to say, I recommend you wait until you've clearly decided.

Thanks for the advice, which is accepted in the spirit with which it was offered. ;-)

Second, yes, I actually have several examples. And I will not use them. Regardless of the example, someone will start complaining that it's too simple, doesn't reflect their own requirements for data munging, etc, etc.

That's the beauty of a case study. Case studies are not proofs or ideals, as I stated they are designed to show something interesting or to lay the groundwork for research into changed practice. Does an orthopedic surgeon complain because a cardiac case study isn't relevant? not unless the Cardiologist insists that a broken femur should be treated the same as a blocked coronary artery. ;-)

What the case study *will* do is allow people to decide whether your experience is relevant to their own practice. If it is (and I think for many it will be) then you will be prompting people to take a closer look wrt their own practice.

Walter has been a critic of SPs and ADO.NET, so I'm giving Walter a chance.

You have been a proponent of SPs and ADO.NET, so I'm giving you a chance.

Expect I'm not, because that would be patronising. I'm asking. If the answer is "no", that's fine, but you can't slam others if their answer is "no" as well.