Leaderboard

As mentioned in the NI forum, the Database Connectivity Toolkit is essentially a wrapper around an ADO ActiveX object. ADO uses an ODBC connection internally and there are syntax differences when using ODBC compared to using MS SQLServer directly: @variable declarations are not supported via ODBC.

Best resource is indeed MSDN: On http://msdn.microsoft.com/en-us/library/yy6y35y8%28v=vs.110%29.aspx you can find information how parameters are used when working with OLE DB, ODBC or MS-SQL in .NET , ODBC in .NET is provided via ADO.NET which is similar to ADO ActiveX. Most important, you can't declare parameters as @param, you have to use a question mark instead and pass all your parameters in the right order. I stumbled upon that when I had to write a data table editor in C#.

Yes, the IDE is stable until a user does something less than ideal, So instead of a user having to learn what will work, perhaps the IDE can teach us what won't work. Perhaps show the user what's taking so long.

This is how I auto increment an executable's version (build # only) in my build script. The child reference of the BuildSpec[] is passed to the Executable Auto Increment Build VI. The Get and Set just read or writes to the XML tags.