10-14-2007 03:47 AM
10-14-2007 10:45 AM
If it works in the development environment, but no longer works as an executable, the problem has nothing to do with priorities. There must be another issue that should be investigated.
What is your LabVIEW version?
10-14-2007 11:05 AM
hey, thanks for your answer -
10-14-2007 12:46 PM
OK.
How do you know that the event does not fire? Could it be that the event fires but produces no visible output? Place e.g. a message dialog inside the event to see if the event executes at all.
How does your event actually print an excel report?
Could it be you are calling a VI dynamically and it does not get included in the build? Are you using relative paths for e.g. some temporary files used to make the report? (see if you use the "current VI path" anywhere, this will need to be adjusted for use in an executable).
Does the target computer have excel installed?
10-14-2007 12:51 PM
10-14-2007 02:41 PM - edited 10-14-2007 02:41 PM
Message Edited by Jarrod S. on 10-14-2007 02:42 PM
10-14-2007 03:42 PM - edited 10-14-2007 03:42 PM
yes i was implying as a general possibility to use timed loop for priorities. i never tried timed loop with an event structure, as i dont see the logic of it. and for the poster problem, this would only apply to the state machine solution.
@jarrod S. wrote:
To my knowledge (which is limited to doing a simple little test), Timed Loop priorities only apply when the loops or their internal frames initially get scheduled. Once any node in the Timed Loop blocks waiting on an event, it won't necessarily respond to that event with the priority you give the Timed Loop. Give it a try by enqueuing values repeatedly into a Queue that two timed loops of different priorities try to dequeue. The priorities don't dictate who wins.
Message Edited by Gabi1 on 10-14-2007 10:44 PM
10-17-2007 06:56 AM
OK,
did put a pop up msg and the msg did poped up when i pushed the botton, so i understood that the problem is something else so i tried to build this simple vi (attached) that only open an excel report.
the report will open b4 the comple but not after ( i have excel installed).
the error indicate this msg :
"Open VI Reference in New Report.vi->Untitled 324.vi<APPEND>
VI Path: <b>C:\Documents and Settings\admin\My Documents\builds\Untitled23\Application.exe\Excel_Open.vi</b>
Built Application or Shared Library (DLL): Make sure all dynamically loaded VIs were properly included in the build specification for the applica"
any Idea?
BTW i have no idea what is "Excel_Open.vi" never saw it.
10-17-2007 07:50 AM
10-17-2007 07:55 AM