LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

calling subroutines

hello

I devided my application in three main parts : test definition, test run and report.
I use a forth vi called master (attached) to call my test vis. The problem is when I try to switch
to an other windows application (I'd like to check if database entrys where properly made)
during my test is running my application crashes.

I've attached my caller vi. I'm sure there is a better way to do this. Can anybody give me a
hint how to change it or where I could find a better solution.

Simon
0 Kudos
Message 1 of 3
(2,578 Views)
I see you running the runtest VI and set the wait until done boolean to true.
Right click the event structure border and select edit events handled by this case option. Unckeck the Lock front panel until event for this case completes and see whether it helps you.
0 Kudos
Message 2 of 3
(2,577 Views)
What is the Windows application that you're opening? Is the database you're using Access? If it is, you could be locking out the VI that is doing the writing. Imho, Access isn't the most robust application and you may need to add some addtional error trapping in your database routines and in case of an error, retry to make a connection.
0 Kudos
Message 3 of 3
(2,577 Views)