application builder changes tdms to excel vi

[ThomasO]

I had a tdms to excel vi that was working great. So I tried to make the whole program into an executable.  I have done this before without incident.  So I went to close the source program and it asked me if I want to save (most specifically the tdms to excel sub-vi).  It was more of a strongarm tactic since I couldn't close it without saving.  Now, both the executable and the source program open the first file, convert it to excel format (as intended) and close it again, but them fails to do it for any other files in the array that I generated.  A little trouble shooting.....  I opened other programs and ran them successfully.  upon converting them into an executable, it asks me to save changes to the tdms to excel vi, which, I never touched.  this resulted in duplicating the problem stated above.

[G-Money]

You might try creating a debuggable executable and then watch the code using Highlight Execution. I have found things in my code that work fine as a VI but not as an executable and this has helped me diagnose and fix the problem.

I don't know specifically what could be happening with your code but post some screenshots and we might be able to assist.

[ThomasO]

I think the issue is not whether or not it works as an executable, but why creating an lvproj changes the source code.

[Doug-W]

If both the source and the executable are exhibiting the same issue, it sounds like something must have changed in the code. Do you still have a properly functioning version of your VI? Can you create a copy and repeat the process on that VI and see if the problem manifests itself again? I'm also going to second Grant's suggestion to post some screenshots of your code so that we can troubleshoot this issue further.

Doug W

[G-Money]

thomas,

          I'm minorly confused so let me ask a clarifying question: Does the VI still function properly but you are just being prompted that "something has changed" by your source code control?

If it's just the "needing to save changes when none were made" issue and not that your code is no longer working then this article (http://zone.ni.com/reference/en-XX/help/371361J-01/lvconcepts/saving_vis_compiled_code/) might help explain why LabVIEW asks for changes. Even though changes aren't physically made by you, there are changes being made.