I can't create a functional executable program for my soft on labview

[Seif.SAFER]

Hello.

after creating a full labview command and control soft for a projet i'm working on, i wanted to make it as executable file to deliver it with the machine to the client. but the exe always shows errors 7. talking about unfound files, but everything is working well through labview. and i'm using dynamic links between VIs. you can see in the links below the methods i use to communicate with ini file and call a VI.

https://drive.google.com/open?id=1Hg79tFxMLSXF-pUskSkletWQhfez2cpB

https://drive.google.com/open?id=1vKN2kSxNGKhIBVfMHmdxDgK2cRtNJbYK

 can you help me to resolve to problem with the executable file?

i can provide parts of the code if it can help someone to resolve my problem.

thank you

[Bob_Schor]

We can see nothing about what you did nor how you did it.  The one thing that is almost certain (I'd estimate 98% certain) is you did something wrong somewhere.

Please compress the folder holding your LabVIEW Project and attach the resulting .zip file.  We need to be able to see all of your code (particularly since you are using "dynamic links" between isolated VIs).  We also need to see how you have built your executable.  It would probably also help if you capture a screen shot of the Error message and attach that, as well (we might not be able to actually run your program as we might not have the hardware you are using, but the exact Error Message would probably have useful information to better enable us to help you).

Bob Schor

[Seif.SAFER]

okey, maybe i made a mistake and didn't noticed it.

u can get all the code using the link bellow:

https://drive.google.com/open?id=1cI4iOgv1KRXkPNNfvTwImwT0dOB5B5CV

thank you

[crossrulz]

---

@Seif.SAFER wrote:

i'm using dynamic links between VIs

---

You probably need to add the dynamically called VIs to your executable.  In the build specification, there is an "Always Include" section where you need to add these VIs.

[Seif.SAFER]

i already did it but it does not resolve the problem 

[Bob_Schor]

I recall (about 8 years ago) wrestling with launching programs using VI Server, particularly when building executables.  I did read the Help descriptions which warned that the "Path isn't what you think it is", that is, the Path for an Executable has to include the Executable in the path name, or some such nonsense.  It drove me crazy, so I started using Start Asynchronous Call, and using Static VI References to create links to the Path Name that worked whether or not I was in Development Mode or Executable Mode.  Problem solved.

I am curious how you have your "opening" routine make a "movie-like" Front Panel ...

I just realized there's a much easier way to do what you want to do.  I'm assuming that there is a real "Main" somewhere that you will eventually start, and that will stay in memory and run everything.  Your "opening" and "Select Version" are really Modal Dialog boxes that get run for a limited amount of time.  "Opening" does nothing except show its very nice Front Panel for 5 seconds -- write it as the first routine that "Main" calls, and have it Display Front Panel when run.  When it finishes (and returns "No Error" on its Error Line), run "Select Version", also as a Modal Dialog Box that returns the Version you want.  If you desired, you can start your Main with its Front Panel hidden (I've never tried to do this, but I assume it is possible), then when Select Version returns to Main, you can "magically" make Main's Front Panel visible, and you are off and running.  This code will work identically in Development and in Execution Mode -- it's just an Ordinary LabVIEW Program, no need for VI Server.  Much simpler.

Bob Schor

[Seif.SAFER]

Thank you for your patience and cooperation.

So if I understood correctly, I have to replace the current path methode to navigate between VIs with static vi reference.

and the problem will be solved after doing this?

Regarding the Opening, it a gif I created, running continuously, I just give it time to execute one time and I lose the vi after doing it.

I know well how to make the main VI open all other VIs, but in this project, I wanted to try a different way of manipulating VIs.

Seif SAFER

[Bob_Schor]

LabVIEW gives you a large set of tools that you can use in different ways to do the same thing.  Sometimes there are "quirks" in one method or another that make doing it one way more "convenient" for one situation, but more difficult for another.

I've tried to adopt a K.I.S.S. (loosely translated as Keep It Simple) philosophy where I code the Main Application as simply as possible and make it the centerpiece of my code -- if I want to make it "fancy" or "pretty", I "add decorations".

That was the basis of my suggestion to you -- start your program with the Main Application, and if it want to begin with a nice Loading Screen, and a set of Dialog Boxes to have the User choose some initialization settings, let the Main "do the driving".  The overall logic of the program will be much simpler, the Build will be much simpler (except for a few Real-Time Projects, all of my Builds had only the Startup VI specified, and everything Built just fine, and none of the code needed to be changed go to between Developement and Execution mode).

Bob Schor

[Seif.SAFER]

Okay, thank you for your advices.

I'll try to adopt the K.I.S.S method, it may be much easier.

Thank you anyway, I'll update it and give you a feedback. Hoping that will solve the problem.

Take a look at the ini file calling VIs, that method do not make problems in the debug?

Seif SAFER