Search the Community
Showing results for tags 'part number'.
Found 1 result
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