I encountered the above error when I tried to run the query,
SELECT MAX(expression )
and then loop through the results using a datareader with code like this,
I got the error above, because when you do a "max" sql query it doesn't return any column header.
All you need to do is give the sql result set a column header.
SELECT MAX(expression) as "ColumnName"
This is another one of my bone head mistakes. It's such a simple little thing I overlook, and gets me so disappointed in myself when I realize I spent time trying to figure this out. It's generally followed by me looking over my shoulder and seeing if any of my peers saw it. I'm mostly blogging this in hopes I won't make a silly mistake like this again.
Why is it always the baby errors that hang me up the most? It can never be something deep in the CLR, or possibly find a mistake in .Net. Nope, noway, not gonna happen .Net is pretty solid...for the most part.