Save data upto completion

[gireesh]

Actually this project is an automated checkout system. It contains so many tests under various conditions. So each tests will show in different window. Thats why I made different VI's.

[Dennis_Knutson]

That does nothing to explain why you made exe's. I'm sure you thought there was a good reason (though I don't know of one) but you've made communication between them next to impossible since you have such an old version of LabVIEW. Write to separate files and merge them later.

[gireesh]

Two +one reasons. 1. Nobody will edit the program (only few people know LabView in our organisation). If create installer, it can install any PC (having same hardware). 2. We can operate Without installing LabView in the target PC. 3. We can make installer CD as for a product launch.

[Dennis_Knutson]

You can call 10 separate VIs and then make that into an exe. The separate VIs could then communiate to each other. Your top level VI that has all of the System Exec functions would be that single VI. Making 10 separate exe's still seems silly. I understand perfectly well the purpose of creating an exe. What you still have not explained is the purpose of creating 10 that you call from another VI.

Making 10 separate dll's would work even better than the separate exe's.

[gireesh]

I tried with dll, I call the dll but it is not worked. I know it is better than this exe.

[gireesh]

One advantage of seperate exe is we can do individual test also.

[Dennis_Knutson]

Well, you never asked for help in creating a dll. With dll's or explicitly called VIs you can still run separate tests if you write the top level VI to do that. That is called creating a test executive and is a very common LabVIEW application.

[gireesh]

Thank you for the advice. Please give more help on that and meanwhile give am example with minimum two window. I will try my level best.

[gireesh]

I get the tutorials about call library and dll. But I cannot understand anything. So many parameters are there inside, what they actually doing, functions etc. Anybody can explain these things, please help me.

[Dennis_Knutson]

I'd have to charge you quite a bit for the test exec I am writing now.

You are using an old, old version I LabVIEW and I cannot save nathing in that version. You can look at the shipping examples for dynamically calling VIs. Generically, if you have a list of VIs, you can use the Open and the Run method and you can select to not wait until done.

I really don't know enough of your requirements to get much more specific.