>>I have posted a question previously about this pathetic error I am getting.<<
To clarify I suspect you are referring to the thread here:
http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/Q_25837130.htmlI re-read the thread and your accepted solution was to the member who asked you if you were using Auto-Close. If I understood correctly you response was:
"Yes... ALL of my databases are set that way. It apparently defaults to TRUE in the creation process. I have not changed any of the default options on any of my databases."
That is not only not true, but a very bad practice. Further I do not believe I am violating any NDA by telling you that the development team tried to remove this feature due to it's "evil" nature, but were forced to leave it for backward compatibility.
I have worked with SQL Server since version 6.5, that is 14 years ago. I have never seen this error in any application, but then again I would never, ever consider setting the Auto-Close on. The only time I have seen it is in SSMS and when I have lost network connectivity. As I told you in your last thread, you can prove this yourself very easily by temporarily disconnecting from the network while using SSMS.
The bottom line and at the risk of repeating myself, is that if you accept the error message at face value and you believe it is in fact a loss of network connectivity, then clearly this is not MS's responsibility. If you believe that the cause is something else and can prove it, I will be the first to contact MS and let them know.
So which is it?