04-28-2011 03:52 PM
Hi Roger,
Was that solution able to solve the error that you're seeing? This is expected behavior, since those VI's are called dynamically. Since it's dynamic, LabVIEW doesn't know where to point the files to, we need to specify it.
Regards
04-29-2011 01:48 AM
In my projects I have many classes and class methods that are called dynamically in exe files.
Usually this kind of error are due to lack of testing with executables generated from the application builder.
This is the _only_ piece of standard NI LV code in my project that behaves like this with the application builder.
Therefore I think this should be considered a bug and handled properly.
Best regards,
/Roger Isaksson
05-11-2011 03:07 PM
I had the same problem. I even added the dynamic VIs to the project by dragging them and it didn't work - you've got to navigate to them directly. When something is that tricky and common, I think that this should at least be mentioned in the help files for the report VIs with a link to the kb
05-12-2011 01:08 AM
What needs to be done in this case is either:
1. Place a "NI_report.lvclass" constant to the vi that handles the "easy text report".
2. Make the application builder automatically include the class if "easy text report.vi" is used.
I dont know which of the two above is worse. But I do know that pointing on a KB article and stating that:
"works as intended" easily beats #1 and #2.
/Roger
08-08-2011 06:07 PM
This issue seems to be fixed in LV2011?
Br,
/Roger