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

Similar Messages

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

Application builder-Office report generation toolkit

Hi,
I remember there was a trick to get the executable work with different
versions of Microsoft office but I cannot find it now. The problem it to get
the exe work with some other office version that it was made. I use LabVIEW
7.0 - 7.1 and Report generation toolkit 1.01 for Microsoft office. Was that
possible?
Thanks Eki

Eki,
When you use the Report Generation Toolkit to build a stand-alone application with the Application Builder, you must add _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs. These two VIs contain subVIs that are called dynamically by the high-level Report Generation VIs. I believe that if you grab these VIs from the (desired office version part of the) installation CD instead of from the development machine, then everything should work.
Zvezdana S.

Error building .EXE Report Generation Toolkit

Whenever i try to build my application this error message shows up.... Error 1502 ocurred at AB_source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass: Save.vi
it says the possible reason is Word_Open_Document.vi
I'm using the report generation toolkit for office.... I really need to build this application soon!!
Please Help!!!
Thx in advance
Wong

I finally made it work... As a reference, i upgraded from labview 2011 due to windows 8 incompatibility, and found that the installer kept showing these error messages.
I read in another post that if you opened the troubled VI and just clicked on the property nodes to browse and then ok, you just saved the VI, restarted labview and the error message disappeared. To my surprise IT WORKED!!! I had to do it on several excell.llb VI's too.
Maybe you could report this bug in the report generation toolkit as a part of the NI team.
thanks!!!
Wong

Error when building a report from 2 different subject areas

Hello Experts,
I am using obiee 11.1.1.5.
I have 5 dimension D1,D2,D3,D4,D5 connected to fact1 and 4 dimension connected to fact2 such as D1,D2,D6,D7.
where D1,D2 is common to both the facts.
Fact1 Is in subject area 1 and Fact2 is in subject area2.
I need to create a report by adding columns of subject area 1 and 2 with columns from all the dimensions D1,D2....D7.
As of now i am getting error stating "No fact table exists at the requested level of detail " when i try to add columns from 2 different subject areas.
Can anyone help me in solving the above problem.
Is there any prerequisite to be taken care when building a report from 2 different subject areas.
Regards,
NN

Hello Nagireddy,
So kind of you, for your quick reply
I was able to solve the error by doing below steps in additional what you have specified
-->For the fact table LTSs, set the logical level in the Content tab to the dimension's lowest level for each conforming dimension (leave the non-conforming dimensions level blank).
Now I have another requirement i,e
I need to have non measure columns such as Date into the newly created fact in BMM layer.
I tried doing the steps which I followed for measure column, but it is throwing the same error which I get earlier.
Below is the error
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14025] No fact table exists at the requested level of detail:
Let me know if have any suggestions

Error 10 when building an application in LV8 and Report generation toolkit 1.1.1

I am trying to build an application using LV8.0.1 and Report generation toolkit 1.1.1 and i get this error.
Error 10 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
Any ideas?
Scientia est potentia!

Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

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

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

Print number of pages with Report Generation toolkit

I use the report generation toolkit and the Print Report.vi to print a table and some text extracted from a MS Access database. The result of this is a print out that takes up several pages.
Now, on each page i want something like (Page x of y), and I do not want to buy more expensive NI packages for this simple thing. I know it should be possible since the Report Express vi can do it --- which for me is a useless vi.
I do not consider it a nice solution to try and keep track of the number of pages myself by dividing the table into more tables and use the new page vi between each "page table". This I would not like to do since depending on paper size, font size, and length of text strings in each cell this will be virtually impossible.
By moving into the Print Report.vi I've tried to see if I somehow can extract the info --- I've not found anything usefull but expect a workaround to possible.
Any suggestions?
Cheers,
Martin

Hi Skinny,
There are some tokens you can use in the headers and footers of Standard Reports generated by the Report Generation VIs. If you take a look at [LabVIEW]\examples\reports\TextReportExample.llb\Text Report Example.vi, you'll see that the right footer text of the report has the token <pagenofm>, which generates a footer of the form "1 of 10", to indicate page 1 out of 10 pages. There's also another tag you can use, <page>, that just lists the page number itself without a total number of pages. If you look at the help for the Set Report Header Text.vi or Set Report Footer Text.vi, you'll see a link in the help for all the different "tokens" you can use with the report header and footer. Actually, now that I think about it, you can use these tokens anywhere in the report, including the body text.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Report generation toolkit VI error when running EXE

A VI inside the Report Generation Toolkit (version 1.1.2), Excel Find Application Directory.vi, will not function correctly when running an EXE. The "Current VI's path" block will return the path of the currently running EXE rather than the path of the Excel Find Application Directory VI. (The same would be true for Word Find Application Directory.vi.)
-Joel
Solved!
Go to Solution.

Have you had a look at this knowledgebase article? The error is caused due to the exclusion of any dynamic VI.
Ipshita C.
National Instruments
Applications Engineer

Report Generation Toolkit and Office 10 - build errors

Using LabView 2011 and Report Generation Toolkit 2011.
After installing Office 10, I would get build error for Excel-Print.Vi and Excel-SetCell.vi and build is then aborted.
2011/vi.lib/addons/_office/_excelsub.llb/Excel-Print.vi.
Says it is unable to save a vi without a block diagram.
Uninstalled Office 10 and reinstalled Office 2003 and build went thru just fine.
I can program using Excel 2003 and the compiled executable will work on another computer with Excel 2011 but once I install Office 10 on my LabVIEW computer I cannot build.
Can't believe I could be the only one to experience this. Any workarounds?

Duplicate Post

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

Hi Leo22,
Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

Problem with report generation toolkit when installed new office 2010

Dear all, I had LabView 8.6.1 and report generation toolkit for MSoffice 2003 perfectly working in my laptop.
Now I have added MSoffice 2010 and report generation toolkit does not work anymore since it is linked to new office.
How can I inform Labview to link report generation toolkit to the old MSoffice 2003?
regards
Max

The Report Generation Toolkit is ActiveX based. When you install the newest version of Office it registers the ActiveX server for that software, which the toolkit adapts to and uses.
Uninstalling Office 2010 would solve the issue, otherwise you will need to look at unregistering the 2010 component of Office ActiveX - but I'm not sure if that's possible.
Regards,
Peter D

Ridiculous number of directories when build includes Report Generation Toolkit

Similar Messages

Maybe you are looking for