LV 8.5.1 AppBuilder error source does not exist

[Leo-Bos]

Hi,

I have a rather strange problem:
Every time I try to to build a VI that was converted from LV 7.1.1 to LV 8.5.1 I get an error that the source does not exist,
although the VI is there and the Preview-build does not throw an error 😕



When trying to build a VI created with LV 8.5.1 the build succeeds of course.
Does anybody have faced similar problems?
The VI and the project should be attached...
thx a lot,
Leo

[JoBa]

Hello Leo,

please open the VI that was created in LabVIEW 7.1 and save it in LabVIEW 8.5.1.

Afterwards, the application should build without errors - it did for me.

Regards,
Johannes Bauer

NI Germany
684462

[Leo-Bos]

Hi Johannes,

I have already converted and saved the VI to LV8.5.1.

Anyway, here are the steps to reproduce the problem:
  1. Open the LV7.1.1-VI using LV8.5.1
  2. Save it with LV 8.5.1
  3. Create a new project containing the VI and having it as startup VI in an Application
  4. Trying to build the application --> leads to the "source does not exist" error

Attached is the source VI (vers. 7.1.1) causing the problem.
thanks in advance,
Leo

[JoBa]

Hello Leo,

I followed your instructions, but was not able to reproduce the error - see the attached application.

However, I can also build the project if I don't save the VI in LabVIEW 8.5.1 first - is it possible you posted the wrong version of the VI?

Johannes Bauer

NI Germany

[Leo-Bos]

Hi Johannes,

thx for your help,
it seems to work when the VI Frontpanel is still open while you're building the app,
but when I close the Frontpanel of Check_Pfad.vi (step 3b 😉 )
and then try to build the application, then the error shows up!?

thx again,
Leo

[gmart]

The VI contains a link to a help file who's name is " " (a space character). In the VI, go to VI Properties>>Documentation. The "Help path" control has a space in it. Delete the space and it should build.

[Leo-Bos]

thx for the resolution, the build works now like a charm 🙂

Maybe the NI crew can alter the Build-errors dialog to see such errors, or prevent such things already in the Documentation-properties dialog, or both of course 😉

Leo

[ceties]

Kudos to you gmart - I just saw the same error and was wondering why that. Would be nice if there was some nice way LV informed the user about that problem...maybe future version.