07-31-2007 06:55 AM
07-31-2007 11:03 AM
Hi FHM,
If LabVIEW spawns the DIAdem instance through ActiveX, then when the VI stops the child DIAdem instance exits too. This is standard ActiveX dependency, and there's nothing we can do about it. However, if DIAdem is already launched and LabVIEW just dials into it with ActiveX, then that DIAdem instance will remain when the VI stops. So one simple solution is to just start DIAdem prior to running your ActiveX VIs.
Alternatively, you can try running the "NI DIAdem Report Wizard.vi" in the LabVIEW-DIAdem Connectivity VIs or the "DIAdem Report.vi" that ships with LabVIEW (on the Express>>Output palette). Both of these VIs create a stand-alone DIAdem instance by invoking DIAdem from the command line with the DOS extension to run a particular script. When DIAdem is launched from DOS it is a stand-alone instance that will continue even after the application that called the DOS command exits.
Hope that all helps,
Brad Turpin
DIAdem Product Support Engineer
National Instruments
08-03-2007 03:53 AM
Hello Brad,
Thanks for your reply. I solved the problem like this:
I am using system exec.vi and give these two comands
"C:\Programme\National Instruments\DIAdem 10.2\Diadem.exe" "/cScriptstart('E:\MY VBS FILE PATH\Daten_Analyse.VBS')"
Now I dont need any activeX VIs.
Thanks again for your reply.
FHM
08-03-2007 04:15 AM
Matthias Alleweldt Project Engineer / Projektingenieur | Twigeater? |