What is the best way to use TestStand/Labview to access database?

[Francey]

Is it best to use the TestStand database step types or use existing Labview database connectivity code to access database?

The database will contain configuration data and results data. I am also not using the standard results collection feature. (Test procedure will possibly last days so I think it is inappropriate to use results collection feature.)

I'm just trying to make my code "future proof".

Thanks

[tbob]

I have used both and I find that it is easier to use the Labview Database Connectivity Toolset. One step in a TestStand sequence can call the Labview vi. If done in TestStand, it takes many steps which I find harder to read and understand compared to Labview code. If it is just a simple one time access, TestStand may be a little easier, depends on one's preference.

[Francey]

---

@tbob wrote:
I have used both and I find that it is easier to use the Labview Database Connectivity Toolset. One step in a TestStand sequence can call the Labview vi. If done in TestStand, it takes many steps which I find harder to read and understand compared to Labview code. If it is just a simple one time access, TestStand may be a little easier, depends on one's preference.

---

Thanks.

I was thinking it would be easier to use the Labview code. I was just trying to sense if the community thought it was old hat and I should be using the TestStand code.