Comments
Sort by recent activity
It was in SSMS only, but that is the only environment that I normally work in / comments
It was in SSMS only, but that is the only environment that I normally work in
It was in SSMS only, but that is the only environment that I normally work in If it makes a differance here is the current release levels SQL Server Management Studio 15.0.18338.0 SQL Server Management Objects (SMO) 16.100.41011.9 Microsoft Analysis Services Client Tools 15.0.19205.0 Microsoft Data Access Components (MDAC) 10.0.19041.1 Microsoft MSXML 3.0 5.0 6.0 Microsoft .NET Framework 4.0.30319.42000 Operating System 10.0.19042 / comments
It was in SSMS only, but that is the only environment that I normally work in If it makes a differance here is the current release levels SQL Server Management Studio 15.0.18338.0SQL Server Ma...
Thank you The work around is easy enough for now / comments
Thank you The work around is easy enough for now
Yes that could very well be the case. Sorry to inconvenience you. When you get that situation, (failure without an identified error) you might want to issue a different error message suggesting an error in the proceeding/following code. I'm sure I am not the first to think Sql prompt was the problem, when it was really my code that was faulty. / comments
Yes that could very well be the case. Sorry to inconvenience you. When you get that situation, (failure without an identified error) you might want to issue a different error message suggesting...
I've tried it and it now works as I had anticipated.
Thanks for you quick response / comments
I've tried it and it now works as I had anticipated.
Thanks for you quick response