From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
08-18-2008 10:36 AM
We are producing for the car industry and the car industry is demanding heavy logging from the first component to delivery and we have to secure, that our logging values are available the next 15 years. It's our responsibility to achieve the demands! We are going to have a central tailored logging database for our product, because
But the database interface in TS is relatively simple and makes the development with Teststand 4.1 unnecessary complicated. There are serveral problems:
The hole database functionality should be overhauled:
Maybe the hole concept based on low level SQL commands isn't really the right answer. I'm open for a discussion and expecting no fast solution. Maybe a version 5.0 will have a better database functionality?
09-03-2008 03:12 PM - edited 09-03-2008 03:16 PM
Hello Eirik,
Thank you for the feedback on TestStand's Database interface. I wanted to address some of your concerns. Also, I am assuming from your forum post you are using the TestStand Database step types.
The TestStand Database step types implement the OLE-DB standard interface for communicating with databases, which is defined by Microsoft. The syntax for calling a database function by using a "SELECT function()" command is not supported by the OLE-DB interface, thus that syntax is not supported by TestStand. You might want to try "SELECT * FROM function()" or using the "Stored Procedure" Command Type in the Open SQL Statement step type (see the picture below).
As for the localization, the Str() function uses the station options setting for localization to format any numbers. You can change this Station Option by going to Configure » Station Options and selecting the Localization tab. You can also call the Str() function and pass the third parameter a '3' to override the station option setting. When you pass a '3' as the third parameter to Str(), you will ensure that Str() will not localize any number regardless of the Station Options.
Lastly, the TestStand Database step types are there to give you a simple interface to databases. If you need something more complex, there is no substitute for creating code in an external programming environments that interacts with your database. These other programming environments will give you much more control over the database operations. Then you can just call these code modules from TestStand.