Comments by jizz (Top 1 by date)

I found this thread because I had the exact same error in an application. The solution I have provided fixed it - so thats all that matters. You must be mistaken sorry. What SSMS implements in the SQL I do not know. But I assure you I had the exact same error & the procedure is correct. I implemented this - no further error & my application works perfectly. So some poor coder may come accross the rambling about the SQL and spend an hour trying to figure it all out. On other sites I have found multiple ramblings about coding the C# to correct the error. All along it is simply corrected in SSMS. Perhaps some people like to look clever when they are afflicted with analysis paralysis & should instead be maximizing the tools available to be productive. Also I dont care if a thread is 1000 years old - if I have a contribution I will make it.