File name collision during build that includes Report Generation toolkit. How to correct?

When I switched to LV 8.6 (it's also in 8.6.1) I started getting a file name collision warning when building an installer that included the Report Generation toolkit. The executable works, but I don't like to leave warnings uninvestigated. I don't understand 1) why it's happening now and 2) what it's recommending for the fix. Here's part of the actual warning it gives.
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...........

Hi GS,
The architecture of the Report Generation Toolkit was changed in LabVIEW 8.6 to utilize LabVIEW Classes. As such, there are some warnings during an EXE build because the class VIs have identical names. Classes were not used in the toolkit in LabVIEW 8.5 and previous...that's why you didn't see any warnings during the build until now.
Your EXE should still function properly, and you shouldn't have to change anything about your build. The purpose of the warnings is to let you know that the duplicate-named VIs needed to be handled differently during the build.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Similar Messages

Ridiculous number of directories when build includes Report Generation Toolkit

I was getting error 7 with the report generation toolkit, so I followed the steps here and it works. Only problem is, it makes a different support directory for each individual file in the NIReport.llb directory.
The calendar and data directories are my own. The rest are the RGT.
Help? haha.
CLA, LabVIEW Versions 2010-2013
Attachments:
buildsetup.PNG ‏49 KB

I set NIReport.llb to always included like it said, but it wasn't showing up after I did a build. So...I left it included always, I created my own destination with the same name (NIReport.llb) on the Destinations page of the app builder, went to the Source File Settings page of the app builder, selected NIReport.llb and set the location to be my NIReport.llb folder I created. I did a build and this solved the problem and all the NIReport.llb files were placed in a NIReport.llb directory. Someone pleaseeee tell me if there is a better way, but this will work for now.
CLA, LabVIEW Versions 2010-2013

Report generation toolkit how to access "title text" 1.1.3

Hi at all,
in LabView 8.5.1 with Report Generation Toolkit 1.1.2 I used the "Generate Report Get Modified Data.vi" and "Generate Report Set Modified Data.vi" to modify the Report Title Text. In the Version 1.1.3 of the toolkit I found no method to access this property.
Is there anybody solved this problem?
Regards,
Nicolas

Mike,
I'm creating HTML reports.
...and I found an unaesthetic solution (thanks to my college):
immediately after I created a new report, I'm searching in while loop for the first report with empty Title Text using HTML Data global.vi (or anything else in the cluster) and the previous HTML Ref-num is the according report. Now I can set the property using HTML Data global.vi again.
I won't suggest this if you're creating reports at more than one place, but in my case I can't get a race condition.
Nicolas

Report Generation Toolkit: How to programmatically insert same values across a MS Words template

Hi,
I currently have written an application that reads information from an Excel/CSV file and key into the Words document.
I did this by introducing a specific bookmark inside the Word document and use the Append Report Text.vi to insert the bookmark.
Now, there are some values where it requires the same bookmark to appear in multiple places. Ie. The same value should be replicated
in many places. I tried to insert cross-references in the template, but whenever the Append Report Text is performed, it overwrites the bookmark.
Hence the cross reference cannot find the bookmarks again.
Another issue is the font size of the replacement. It seems that it keeps on replacing it at Font 10.
Whenever the above VI is called. Is there a way to retain the same bookmark font as per what was saved as the template?
Thanks & Best Regards,
Kah Wai

I think I manage to resolve this using the VI created by Henrik Volkers
http://forums.ni.com/t5/LabVIEW/How-to-edit-text-in-MS-Word-HEADER-using-bookmarks/m-p/1477060#
Sorry for the post

Using the report generation toolkit, how do I make a bar graph verticle instead of horizontle?

The attached vi is similar to what I am using, and it produces an Excel bar chart. I would really like to create the same chart, only vertically instead of horizontly. I have tried all kinds of things that don't work. Is there a way to do this that does work. I want a result similar to rotating the produced chart 90 degrees CCW.
Thank you!
Attachments:
Chart Test.vi ‏20 KB

you want to use a xy-graph.
you can right click the plot legend to make a bar graph vertical.
Harold Timmis
[email protected]
Orlando,Fl
*Kudos always welcome
Attachments:
bargraph2.jpg ‏91 KB

Report Generation Toolkit with Excel 2003 and Excel 2000

Hello,
I'm using the Report Generation Toolkit to generate an Excel report from an Excel template.
The "NI_Excel.lvclass" is included in the "source" section of the application builder options.
I create an exe file on a PC where Excel 2003 is installed. On a Notebook, where only Excel 2000 is installed, the application crashes at the generation of the report:
I guess the problem is the different version of Excel but I don't know. On the developer PC with Excel 2003 it works fine.
In this document it's only talked about different Word versions.
How can I use the Report Generation Toolkit here?
I'm using it that way:
Regards

Oh, it seems that the Report Generation Toolkit "only" supports Excel XP/2003/2007.
I think, that's the problem.

Excel value range with Report Generation Toolkit

I have an excel sheet. I want to find out the range for cells with values. At least, I want the find out what's the last row that has values in it. I tried "Excel Get Last Row.vi" in the report generation toolkit, but it would treat a blank cell as a valued cell if it is filled with another color. Therefore, that won't work.
I don't want to use active x, and I don't want to write a separate vi to search for the last row. I want to see is there a way to use the report generation toolkit. Can I somehow get a hidden method from the class? I would think that, since they are charging for the report generation toolkit, a simple function like that should be included. Thanks!
Kudos and Accepted as Solution are welcome!

I am pretty sure that the Report Generation Toolkit does use ActiveX, so you are using it even if you dont want to.
Seems to be how the UsedRange function is being used in the toolkit.
See here for some examples: http://blog.contextures.com/archives/2012/03/01/select-actual-used-range-in-excel-sheet/
I tried, and it does not find the blank cells with colored backgrounds.
This will require some activeX modifications though.
Kenny

MS Office Report (Report Generation toolkit) is not executable, Xnode broken?

Hi, I am trying to generate an excel report, and I figured it would be easier to use the MS Office report VI, but I am getting the broken arrow saying the SubVI is not executable and that the library that defines the xnode is broken... here is a screensot attached, I already uninstall and reinstall the report generation toolkit and still the same... this is what I found on NI: "This error occurs when the library that defines the XNode you used is broken. To correct this error, reconfigure the XNode." but no idea how to reconfigure xnode
Attachments:
Error.png ‏67 KB

What version of LabVIEW are you using?
What is the nature of your Report? What should it look like? What kind of data should it contain?
Can you show us some code that you've tried to use? If so, include the code as either a Snippet or as a VI attachment (so we can plug it into our own LabVIEW installations and experiment with it).
I generally find that the Report Generation Toolkit is a very easy way to generate Excel Workbooks. I work primarily with LabVIEW 2012 and LabVIEW 2014.
Bob Schor

Built labview report generation toolkit cannot run

Hello everybody,
I would like to ask some questions on report generation toolkit:
The program works well in developing mode.
Then I can build the program into *.exe file.
However, all functions related to report generation toolkit are not working after I built them into *.exe file.
(i.e. The program can control equipments and calculate, but cannot open an excel report and write something in it.)
There are no errors when building the program.
Is there something wrong with the toolkits or is there some advance settings?
Thank you very much for your help.
Best Regards,
Donald

Including Report Generation VIs in Stand-Alone Applications (Report Generation Toolkit)

Problems in using Application Builder to Build a exe file with Report generation Toolkit

Hello,
It's my first time to build exe. But I have Problem when the VI have Report Generation toolkit VI.
It's no problem in VI Format , But It can't work when I build as EXE format
Can Anyone help me, and state step clearly in how to solve the problems?
Thank you!!

If the code works OK in the development system but not in an executable there are a few things you can check. The two most likely causes are:
There is an error occuring that your code isn't reporting.
There is a file path that under the executable isn't valid.
First make sure that all the error clusters are daisy-chained together in the subVI that you wrote to create and populate the excel file. Next make sure that the end of that chain goes to an indicator on the VI's front panel.
Second, make sure there are indicators on other key parameters like the path the file is trying to write to.
Third, temporarily modify the VI properties of that excel IO VI to open it's front panel when called, and rebuild your application. The next time you run the application the front panel will open when you try to write to the excel file and you should be able to see what is happening.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Framemaker uses $filename for short file name, can we edit this to change appearance? We do not want the short file name of long filename to include the .fm extension can this be removed or modified to make this happen?

Framemaker uses <$filename> for short file name, can we edit this to change appearance? We do not want the short file name of long filename to include the .fm extension can this be removed or modified to make this happen? In compiling our books it would be helpful to not have this extension appear as it then requires us to create extra files without them.

See: System Variables

Problem building application using Report Generation Toolkit, LV 2011

I'm using LabVIEW 2011 under Windows 7.
I tried to use Application Builder to create an executable from a large body of code. One thing the application does is load VIs into a subpanel and run them.
Application Builder created the executable and gave no error message. The built application ran except that it couldn't run any of the dynamic VIs.
I finally succeeded in doing a screen grab on a transient dialog (about 1/10 sec. appearance). The dialog showed an attempt to load <vilib>:\Utility\NIReport.llb\NI_report.lvclass.
In one dynamic VI I commented out the call to the only VI that uses the Report Generation Toolkit (called only from dynamic VIs, all of which call it). Sure enough, when I built the application with that change and ran it, the dynamic VI that didn't invoke the Report Generation Toolkit did successfully load into the subpanel and run.
So, trying to prove to myself that that was the only problem, I wrote a VI that does nothing but load a VI into a subpanel and run it. User can choose one of two VIs: one that doesn't call the Report Generation Toolkit (or do much of anything), and one that does. Both VIs run fine standalone.
The not-much-of-anything VI loaded and ran in the subpanel. The other VI didn't--the same dialog, mentioned above, popped up for 1/10 second or less. Screen grab is attached.
When I included LVClass and NIReport.llb folders in the project (from vi.lib\Utility: Snapshot folders), and "Always Included" those folders (per a suggestion on this forum from a few years ago), the result was the same. The result was also the same when I included either one of those folders but not the other. Likewise it doesn't matter whether I add the dynamic VIs as "Always Included" or not.
Another piece of information that may be pertinent: when adding the NIReport.llb folder, I got a message that it was impossible to add a certain VI that's part of some report-type class, because a VI of that name already existed in the project. Screenshot of that dialog is also attached.
VIs and project file are also attached along with the two screenshots. I hardcoded VI paths, so put everything into C:\Testing if you want to see what the code does--or hack as desired, etc.
I will be deeply grateful for any help! And I apologize in advance if there's already some exact or close-enough solution posted--but I doubt there is. I looked around.
Thanks very much,
mws
Attachments:
Test-App-Build.zip ‏336 KB

Hi again,
If you extract all files in the original zip attachment to a folder called C:\Testing on a Windows 7 machine running LV 2011, and then use the build script within the project file to build the application, you can run the application and see what happens. You can also play around with the build parameters, rebuild, run, and see what happens then. You can also open my VIs and see what I'm doing.
The application lets you pick one of two dynamic VIs to run in a subpanel. One VI contains calls both to Report Generation VIs and some functions from the Advanced File Functions palette. The other VI does not.
When you pick the first VI to load and run (the one with the Report Generation and Advanced File Functions calls), it loads into the subpanel but is not executable.
When you pick the second VI to load and run, it does load into the subpanel and execute. So there's nothing wrong with the way I load and run a VI in the subpanel.
In the development environment, the whole thing runs with no problems.
Evidently the built application has problems resolving paths of something called by Report Generation VIs and by the Advanced File Functions I use.
I've done a lot of experimenting and no luck. I've looked in forum archives, etc. etc., for possible solutions. I'm hoping there's some simple solution I've missed.
Thanks very much for any help!

Report Generation Toolkit and App Builder question..

Hello,
I am in process of modifying my test code for writing my data to Excel. When I first developed the tests I did not have the Report Toolkit of Excel so I built the ActiveX VIs I needed. Now since I have upgraded to 7.1.1 with the MSOffice Toolkit I am rewriting my test code to use the toolkit VIs as it seems to work much better and faster then what I had done.
My question is this. Since I have my testcode distributed to multiple machines when I build my App, do I need to add every Dynamic VI within the toolkit to my App? if so is there and simple way to find exactly which dynamically called VIs are used within the toolkit VIs?
Thanks
Jeff
Jeff D.
OS: Win 7 Ultimate
LabVIEW Version: 2011,2010,2009 installed
Certified LabVIEW Architect

Greetings jdebuhr ,
I'm using LabView 7 and have the report generation toolkit, In the "Report Generation Toolkit User Guide.pdf" manual under the title Cearating stand alone applications you 'll find the names and the path of the required dynamic VIs to be included in your EXE file (using appliocation builder)
Check this manual.
Ayman Mohammad Metwally
Automation Engineer
Egypt - Cairo

Report Generation Toolkit and Application Builder

I am going insane trying to work this out.
I am trying to build an EXE program using Application Builder. The program uses the Office Report Generation Toolkit.
I have tried including the dynamic VIs into the project, both from the Development machine and from the CD. I still have the same problem : the application does not start Excel. It is like the commands go into a black hole. There isn't even an error message.
I have attached my report VI for you to peruse. Any help is appreciated.
Brian Rose
Solved!
Go to Solution.
Attachments:
TestReport.vi ‏122 KB

Yes, Labview 8.2
Office Toolkit = 1.1.1
I have tried many combinations of what files are included, from just the top level VI, to every VI in the heirarchy tree (a major pain). I am now trying to rebuild the project from scratch and see if that does anything.
Brian Rose

Report Generation Toolkit producing error -2147417842, "The application called an interface that was marshalled for a different thread."

Hi everybody,
I've got an application that logs data to an Excel spreadsheet using the Report Generation Toolkit. My VI's have worked fine in the past using Excel XP, but since I've upgraded to Excel 2007, I am getting COM errors like this one:
"Error -2147417842 occurred at The application called an interface that was marshalled for a different thread. in Excel_Insert_Text.vi" That is the exact wording, even with the weird punctuation and capitalization.
The first occurrence of the error is not determinate. Sometimes, up to 10 logging sessions, involving a new .xls file, can occur before this error pops up. Once this error occurs, I must quit LabVIEW to resolve it. If I try to do anything with Excel, I always get this error, although sometimes it comes out of different source VIs. Excel_Open.vi is another.
These logging VIs have worked just fine until upgrading to Excel 2007. I checked, and I was using a really old version of the Report Generation Toolkit, v1.0.1. I read the documentation and had a big sigh of relief when I realized I needed to upgraded to v1.1.2 to get Excel 2007 support. However, even after upgrading, I'm still getting the same errors. I'm using LabVIEW 8.0.1, and I'm also building these VIs into an application. The error occurs both in the LabVIEW IDE and in the built application. Does anybody out there have any idea what I can do to fix this? I googled a little, and discovered this is a COM error, but I can't find any references to the Report Generation Toolkit specifically.
Thanks,
Phil
Solved!
Go to Solution.

Hi Christian,
I do not see that exact option listed, do you mean "user interface"? I recognize the "Run in UI Thread" option, it's on the Call Library Function Node.
I checked, and my top-level VI has "same as caller" set, and I believe all my VIs are set to "same as caller". Are you suggesting I change my top-level VI preferred execution environment to "user interface", or just the logging sub-VIs that use the Report Generation Toolkit?
Thanks,
Phil
Attachments:
VI_properties.png ‏15 KB

File name collision during build that includes Report Generation toolkit. How to correct?

Similar Messages

Maybe you are looking for