Build name conflicts (NI Report Generation Toolkit)

[Peachy]

Hi,

When I build my application, I have a Warning message about name conflicts. All the files are related to the NI Report Generation Toolkit. I'm using LabVIEW 8.6 and Report Generation 1.1.3. The application works, but in the folder where is the .exe, there are folders related to the Report (NI_Excel, NI_HTML, NI_report, NI_ReportGenerationCore, NI_ReportGenerationToolkit, NI_Standard Report and NI_Word).

In my project, I use these VI: NI_report.lvclass:New Report.vi, NI_report.lvclass:Append User Formatted HTML to Report.vi, NI_report.lvclass:Save Report to File, NI_report.lvclass:Print Report.vi and NI_report.lvclass:Dispose Report.vi.

Here's the warning message I get:

LabVIEW prevented a file name collision during the build. Duplicate file names cannot be copied to the same destination. You can rename files as part of the build process to avoid name conflicts.

The following files were moved to a unique location:

C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append Control Image to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append Control Image to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append File to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append File to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append Horizontal Line to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append Horizontal Line to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append Hypertext Link Anchor to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append Hypertext Link Anchor to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append Image to Report (path).vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append Image to Report (path).vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append Image to Report (string).vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append Image to Report (string).vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append List to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append List to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append Numeric Table to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append Numeric Table to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append Report Text (num).vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append Report Text (num).vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append Report Text (str).vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append Report Text (str).vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append Text Table to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append Text Table to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append User Formatted HTML to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append User Formatted HTML to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Clear Report Text.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Clear Report Text.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Clear Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Clear Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Get Report Settings.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Get Report Settings.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Get Report Type.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Get Report Type.vi
 etc..... (I can't write them all because I exceed the max characters)

How can I take off this warning and not having the folders where is my application?

Thank you

Stephanie

[Hillman]

 Hi Stephanie,

When using the Report Generation Toolkit 1.1.3 under LV 8.6 and creating an EXE you get a warning “LabVIEW prevented a file name collision during the build. Duplicate file names cannot be copied to the same destination. You can rename files as part of the build process to avoid name conflicts.”. As a consequence, some folders are created in the EXE-folder NI_HTML, NI_report and NI_Standard report).

There is a CAR #101700 but it was closed because it is "expected behaviour".

The report generation toolkit is now class-based, so that support-VIs must be swapped to EXE-folder. The double filenames are consequences of the class-based-approach. You can minimize the files as work-around.

Here are some using links on the warning and how to minmize the warning.

Managing the Resulting Files from a Build Containing LabVIEW Classes

http://digital.ni.com/public.nsf/allkb/47272B69E2C167DB862574AC006A258B?OpenDocument

Name collision error occurs when building executable
http://digital.ni.com/public.nsf/allkb/FB9A11C924883B0C8625742D0059D55B?OpenDocument
 

Please let me know what you think,

Kind Regards,

[Peachy]

Hi Hillman,

Thank you for your help. What I did to solve my problem was:

In my project I've added "NI_ReportGenerationToolkit.lvlib", "NI_ReportGenerationCore.lvlib", "NI_Excel.lvclass", "NI_Word.lvclass", "NI_HTML.lvclass", "NI_Standard Report.lvclass" and "NI_report.lvclass". In the build properties -> Source file settings, I put a prefix to all the folders. Example, in the NI_Excel.lvclass there's a Excel folder. On the right you add NI_Excel in the prefix field. In the NI_Word.lvclass there's a Word folder and I add NI_Word as a prefix. I do that for all the folders.

Now when I build my project, I don't have any folder related to the Report Generation and no more warnings.

Stephanie

[Hillman]

Hi Stephanine,

Thanks for the update and Im glad it works!

Thanks also for using the indicate answer function.

Kind Regards,

[Andrey_Dmitriev]

Hi, Peachy,

You wrote: "...I put a prefix to all the folders..."

Is your application working properly after such "intrusion"?

I ask because inside of Report Generation Toolkit the paths coded in such way:

So, you can get troubles with adding prefixes to all files by build (at least this way not working for me)

Andrey.

Message Edited by Andrey Dmitriev on 11-04-2008 07:01 PM

[Peachy]

Hi Andrey,

You are right, I didn't try it and I thought it'll work, but unfortunatly, I get the error 41000....

I'll try to find another way to solve my problem...

Thank you,

Stephanie

P.S. How you take off the "Accepted Solution"?

Message Edited by Peachy on 11-04-2008 12:41 PM

[gmart]

I want to emphasize that the original post was about the warning message. Again, this is a warning not an error. Your application should run properly. 

Aside from the coded path in the Report VIs, renaming VIs that are part of a class will break inheritance since the name is what is used to dynamically dispatch VIs. So while you eliminate the warning message, your built application may not work properly.

You can rename conflicting VIs that are part of project libraries as part of the build since the naming restriction is not applicable.

[pfhenry21]

I'm sorry but the expected behaviour is quite big, even when I called NI France for support on that problem they didn't know.

Do you feel ok to provide to customer a executable with VI on the support folder ? 

for me, not really. I would rather prefer everything inside the executable, it's much more clean and professional.

that's not normal to provide the new report generation as it's steel not stable !

what solution for the future stay with these warnings messages until the new version ?

for the price we pay the developper suite, I don't really appreciate that...

[Peachy]

Hi George,

I understand that it's only a warning. My application run properly but I have 7 additionnal folders where is my .exe and it's only because I used few Report Generation VIs.

I feel the same way as Henry. It will be great to fix this problem even if you don't think that's a huge issue. When we install our application in a customer's computer, it's great to have only the .exe and not several folders.

Hope you understand,

Stephanie

[gmart]

I apologize if my post implied your concern was not an issue. I was addressing the first part of your post regarding removing the warning,

It is completely understandable that having files outside of an executable is not desireable. It is an issue that is actively being investigated. The knowledge base referenced below is a workaround to try to reduce the visibility of these additional files.

Managing the Resulting Files from a Build Containing LabVIEW Classes

http://digital.ni.com/public.nsf/allkb/47272B69E2C167DB862574AC006A258B?OpenDocument