Jump to content

Search the Community

Showing results for tags 'part number'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help


  • *Uncertified*
  • LabVIEW Tools Network Certified
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
    • Custom Probes
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Personal Website

Company Website

Twitter Name

LinkedIn Profile

Facebook Page



Found 1 result

  1. Hi, I have a big project to manage which includes :-TestStand + LabVIEW-SQL Database for test inputs (UUT characteristics, sequences parameters,...) -HTML Reports -almost 10000 different part numbers (that's THE point) with common characteristics (almost 3000 families) + specific characteristics Everything has to be imaginated. The SQL inputs tables have to be created. The number of sequences to code has to be reduced to the minimum because, of course, it's impossible to code 8000 sequences differents files... The final solution must be as simple as possible. Possible ways of reflexion : -XML and Xpath for families and their children -Intermediate LabVIEW OOP layer for families and their children -Dynamically created sequences + variables (TS scripting)-Dynamically created sequences (concatenating a bunch of generic sequences to build a specific sequence) There is a lot of documentation about TestStand and SQL, but only for results (outputs), not really about inputs. Does anybody manage this kind of project ? In which way ? What would be your advices ? Thanks, Sébastien CLA
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.