I agree with all of the complaints in this thread.  I too have the same issue and feel that this bug should've been fixed long ago.  I also am a programmer and having an easily repeatable, consistent bug like this should not be difficult to resolve.

I am respectfully requesting that this bug report be escalated back to the development team for review and action.  Not only to resolve this issue but if the code contains a flaw that allows this error to be present just by having SQL installed on the same system, then the QB application risks corrupting not only it's data but also risks corrupting the external data or configurations for the SQL instance as well!!