With pleasure
1)
unzip and open the list of combinations.vi,
(LV2013 has been used)
set the control "set to 1000 for debug mode" to 1000 and run the vi,
this would give you an over view of the logic used (in about 2 to 3 minutes)
you could use the lv debug mode, but it would take longer.
it is set to give you an output of 72 rows.
the settings or the column contents and the number of possibilities in each column of the output array are defined in the "master settings sheet.csv" in the support folder
2)
open the macro enabled workbook "master setting sheet.xlsm"in the support folder
run (debug first) the macro "prepare_table"
*the sheet "setting"contains the same definitions
*the TEST sheet will contain the output
*to debug the macro, press edit instead of run and use F8 key for step by step debugging
you will be able to notice that the logic is almost exactly the same in both LV and macro.
to experience the time difference,
replace the contents of the "setting" sheet of the macro workbook and the contents of the "master settings sheet.csv" with the contents of
"settings for longer execution periods.csv"
in LV the time of execution is displayed by appropriate control in ms
in macro, the time is displayed via a msg box at the end of execution of the macro.
the intermediate times of executions have been obtained by appropriate contents of the settings sheets, (product of elements of 1st column = number of rows)
suggestions to improve style of coding in both platforms is very welcome.
Would love to understand the reason for the difference in execution time (frequent front panel updating is not the problem)
Thanks a lot.
