Database Connectivi​ty Toolkit does not even load in labview 8.5

Question

When you do a clean install of labview 8.5 on a computer and try to load an app using the database connectivity toolkit, you get this error:
This comes up for multiple vi's in the database connectivity toolkit.  NI is still shipping labview 5.1 toolkit vi's with the 8.5 release. 
-Devin
I got 99 problems but 8.6 ain't one.

Answer 1

Don't lecture me about all software having bugs.  NI is obviously imploding under its own weight.  Its one thing to have a couple of bugs here and there, but NI needs to maintain and follow a release process that includes significant beta testing and a careful review process.  If NI expects labview to be used in production-critical areas across more and more industries, they need to work much much harder on quality control.
The database connectivity toolkit broke when the release labview 8.0.  This broke every application I had.  Sales reps assured me they would fix the problem.  Applications engineers assured me they had entered the bug into teh system and that it would be fixed. 
You can't even OPEN the database toolkit in labview 8.5.  So no, its pretty obvious no one at NI ever even opened it to check its functionality with either 8.0, 8.2, or 8.5.  They would have seen this problem!  You can't even load the toolkit because the vi's are verison 5.1!  If my software had this kind of quality I would not only be a very poor engineer, but I would also be ashamed of myself.  I would be embarrassed.  If you software is like that, then you should be ashamed of yourself too.
Your argument, "all software has bugs" is basically saying I should be passive and accepting of whatever NI gives me for my $4000 a year.  I am demanding better quality control.  Are you suggesting there is no point in this demand, and to just accept the fact that all my applications will break each labview release?  And for the record, my software works when I deliver it.  Any bugs that have a functional impact have been found and fixed before I deliver product.
I'll give an example:  Each time I try to build an exe in labview 8.2, the build has an error.  A sub-vi is missing.  A sub-vi broke during the build.  Each time I have to mass-compile.  Every now and then it works after I mass compile and re-save-all.  But usually I have to copy an entire vi to a blank vi and re-save it under the existing name.  Often I have to do this to multiple vi's, each time trying to build an exe and failing after 20 minutes of the lengthy build process.
Its WEDNESDAY.  I've been trying to build an existing app into an exe since MONDAY.  This happens every single time I change something.  I have EVERY RIGHT to complain.  This is costing us a lot of money.
When it takes hundreds of hours to rework every application I have, including thousands of vi's every single time NI has a new release, its not worth purchasing the next release then is it?
Message Edited by billings11 on 10-24-2007 02:15 PM
Message Edited by billings11 on 10-24-2007 02:21 PM
-Devin
I got 99 problems but 8.6 ain't one.