Another interesting pain in the ass issue with Visual Studio 2005 concerns the control flow containers in the tool box. Discovered only after much angina that I couldn't drag them into the control flow area with the mouse like you can all the other items. NO! Not the high and mighty containers! No dragging them around like common tasks! To get one of them to deign to inhabit your control flow you have to double click on them.
Why, Microsoft, why?
Tuesday, June 12, 2012
Bugs in a Microsoft program? Nawwwww! Couldn't be!
I've been expanding my abilities in SSIS programming, but at present am forced to use the aging Visual Studio 2005 for such endeavors. Well looky, looky if I didn't find a major bug, and thankfully, the fix for it, while playing with a Forloop Container.
The nasty lil' ole bug is in the Script Task Editor, when you go to click on Design Script. The Editor simply closes and leaves you stranded looking at the control flow screen.
The fix, which I found only a couple of mentions of on the web, is to download and install the SQL Server 2005 Service Pack 3 patch.
As of this writing it's still available at: http://www.microsoft.com/en-us/download/details.aspx?id=14752
For my aging XP desktop, SQLServer2005SP3-KB955706-x86-ENU.exe was the file of choice.
So far, I've noticed nothing else screwed up by whatever it installed.
Despite my fears it would, it didn't kill my more recent Native Client that my php scripts depend on.
and my more recent Visual Studios appear to be working fine.
The nasty lil' ole bug is in the Script Task Editor, when you go to click on Design Script. The Editor simply closes and leaves you stranded looking at the control flow screen.
The fix, which I found only a couple of mentions of on the web, is to download and install the SQL Server 2005 Service Pack 3 patch.
As of this writing it's still available at: http://www.microsoft.com/en-us/download/details.aspx?id=14752
For my aging XP desktop, SQLServer2005SP3-KB955706-x86-ENU.exe was the file of choice.
So far, I've noticed nothing else screwed up by whatever it installed.
Despite my fears it would, it didn't kill my more recent Native Client that my php scripts depend on.
and my more recent Visual Studios appear to be working fine.
Subscribe to:
Posts (Atom)