I think your code is well written and I have enjoyed working with it trying to figure this out. thank you for taking the time for the code to look neat.
I cannot break this code with the sample database that I have on my computer so I am guessing it would be smart to look at the problem from this angle.
You may be using a reserved word or need to use a delimiter to handle table or field names containing a space. If this does not help please respond back and let me know.
to anyone looking at this thread I feel that I have tried hard and would love some help figuring this out.
Uninstalling the 2011 Database Connectivity Toolkit, reinstalling the 2010 Database Connectivity Toolkit, and pointing my VIs to reference the VIs from the 2010 folder.
Oh wow, for some reason I was able to get the code to run on my computer with the 2011 Connectivity toolkit with Labview 2011. We could spend forever trying to figure out exactly what happened. Instead I think we should rejoice that it is working now. I am glad to hear you solved the problem. Well done!
I have the same problem. Calling a stored procedure used to work fine with 2010. I upgraded to 2011 (LV and DB) and this error occurs. I checked everything and found nothing wrong. The procedure still works from C# and SQL Server manager. In lieu of a better solution I'm going back to DB 2010. Will post if this doesn't work.
I'm curious: what upgrade method did you use? Looking back, I think I downloaded the 2011 update before getting the CDs in the mail. I'm just wondering if that might be a commonality between our experiences.
I just completed a downgrade of the DB conectivity toolkit (2011 to 2010). This also repaired the issue for me. All of my call stored procedure sub-routines are now functioning correctly again (in dev enviro and as built exe).
