executable from project

[greghicksoz]

G'Day

I am trying to create an executable from an operable VI.

When I try to use the EXE on the same PC as the development environment, it fails to do anything beyond a quickj jump into runing then falls over.  There is no error message that I know of so I am stumped where to start to fix this.

If I can ask for some guidance on where to look, it will make a world of difference.

I am sure that I included everything I has created, but there will always be more (won't there....)

[greghicksoz]

PS - LabView 8.0.1 Full Development Suite

[Jarrod_S.]

The first place to look with all executable errors (even if no message pops up) for applications that work fine as VIs is in the file paths used. If you reference a file using a relative path (for instance, using the same directory as the VI opening the file), then you have to take into account that this relative path will change when the VI gets built into an executable. This happens because the VI is now located in the exe file itself. So if you strip the VIs path, you get myApp.exe or whatever instead of the directory name you're expecting. Are you doing any file IO?

[greghicksoz]

Jarod

Thanks for your assistance.

There is only instrument IO (USB) at this point, there is no pathing involved (and I know how to use API calls to extract what I am after there)

More details as this is more complex than meets the eye.  Some of my sub VI are in an LLB and after a late night I am thinking the problem may be related to the VI's from the LLB.

I have had to spend a lot of time with the schematic and was thinking the symptoms were initially saying the driver was not present, but that part is not true at all.  Now I am thinking the above is more likely to be the culprit... maybe time we bugged NI's LV Engineering group to add this functionality to the builder to extract what it needs from the LLB and save us the trouble....

Let me know your thoughts on this, thanks

[Dennis_Knutson]

I'm not sure what you mean about VIs in an llb. If you are not calling these subVIs dynamically, subVIs in an llb, in a folder, or in multiple llbs, will be automatically included in the exe build. You can verify this by renaming the exe to llb and using Tools>Edit VI Library to view which VIs are there. Now, if you are dynamically calling some VIs, different rules apply. Please explain how the subVIs are called.

[greghicksoz]

Dennis

I am using someone elses product and I don't dynamically load anything in my VI.

But I think I saw a node in his work where some of the VI are loaded dynamically.

I am probably not aware enough of how the builder operates and its limitations (in spite of reading a lot), but I did pick up that the dynamic load VI need to be added to the dynamic listing.  Perhaps that is the thing I was missing.

regards



Greg Hicks