run vi asynchronously causes on the fly reporting header to mess up

[GarryG]

Hello,

I'm using run VI asynchronously to open a prompt to alert the user to wait while other things are happening under the hood.  When I have these asynchronous steps running in normal mode (not skipped) the header of the XML report (and at least the ASCII report too) is missing the start date and time and the status (even after execution is completed) says "Running".  When I skip these steps, the report comes out just fine.  This only happens when reporting is set to On the Fly (when not On the Fly, the report header is fine whether the steps are skipped or not). 

I'm using TS 2010 sp1.  (I don't currently have the option of using 2012).

I appreciate your ideas!

[dug9000]

Are you waiting for the asynchronous VI call to complete before your sequence completes? Either with the automatically wait checkbox set or with a wait step set to wait for a thread.

-Doug

[GarryG]

Yes, I am waiting for the Thread to Complete via the checkbox and closing it by setting a local in the sequence with a statement step at the end of cleanup.  Also, I should disclose that this is happening in a sequence in another sequence file (a secondary or support process model), not the primary process model or client.