Report Generation Toolkit Evaluation doesn't work

Hello,
I tried to insert data into an Excel file but it seems the Report Generation Toolkit Evaluation doesn't work.
Attached file my VI.
LV is saying i have to activate the product in order to run it. An error occurs on each Report Generation subVI, which involve i never could test my application.
I went on Help/Activate Labview component and the evalution is well activate.
Someone has an idea why the evaluation version doesn't run Report Generation Toolkit ? A solution asap please...
PS : I still have 15 days evaluation left.
Solved!
Go to Solution.
Attachments:
Test_insert_data.vi ‏9 KB
Test.xls ‏14 KB

UP
With message failure
Attachments:
Sans titre.JPG ‏50 KB

Similar Messages

Exe created with Report Generation toolkit does not work for all users

I created a exicutable with the report generation toolkit and it only works with some of my users. I use microsoft 2007 and anyone that has microsoft 2007 my exe works well. Most of my users that have microsoft 2010 are able to use my program as well. However, there is one user with 2010 and Windows 2007 that cant get my program to work.
Any suggestions for troubleshooting this?
Thanks

The most likely issue is due to the fact that Microsoft changes the ActiveX object model of Office for each version of Office. The Report Generation Toolkit does a pretty good job of handling this, but it is not 100% effective. Search, for example on the "Set Cell Border" function and you will see what I mean. In these cases it's up to you to handle this issue. How you handle it really depends on your situation. For us to provide a more concrete answer you will need to provide further details, such as what toolkit function is "not working" (whatever that means), and who you "users" are. Is this an internal distribution? Are you selling this program? Is this code written for a project with a specific customer?

Report Generation Toolkit failure with Win 7 and Labview 2013

I recently had my computer updated to Windows 7 and am now seeing a problem with the Report Generation toolkit (version 2013) when working with Excel files. If I try to run the New Report.vi with report type Excel selected I get error -2146777998. Doing the same thing with Word selected eventually opens Word, although this takes about ten seconds, but it does not generate an error. Selecting Standard Report or HTML also run without errors.
I've researched this error on line but I keep ending up .NET and C# forums where everything goes over my head. Has anybody got any suggestions?
Solved!
Go to Solution.

I found the solution to this particular source of error code -2146777998. There are two template files that reside in C:\Program Files (x86)\National Instruments\LabVIEW 2013\templates\Report by the name of MSOffice_RGT_Template.dot and MSOffice_RGT_Template.xlt. The problem came down to that these templates got corrupted somehow during the fresh install. As soon as I replaced them with versions from another machine the problem disappeared.
Just as a side note, I discovered the problem by kicking off the MS Office Report Express vi and out came a much clearer message that aimed me at the templates. Not quite sure why that message isn't echoed into the individual subvi's on the pallette, but life is a mystery.

Unable to write an image to excel with report generation toolkit

I am unable to write an image to excel with the report generation toolkit. The VI works fine for word, but when I select Excel the speadsheet pens but remains blank.

Ranjeet
I am using Labview 2013 or 8.0, but here is an image of the very simple test VI.
Regards
Steve

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

Report Generation Toolkit doesn't work after patches A thru I.

For LV7 Express, RGT demo doesn't run any of its operations, Word, Excel,... See attach for cause. Can anyone tell me how to fix this?
Attachments:
RGDemo1.doc ‏36 KB

Hi,
When you get this error, it's normally because the version of the Report Generation Toolkit VIs in your VI that you are trying to open is different from the one on your PC. Normally you can just right click on the bad VIs on the block diagram and choose "Relink To SubVI".
There's a KnowledgeBase that describes another issue when using different versions of Microsoft Office.
Best regards,
Philip C.
National Instruments
- Philip Courtois, Thinkbot Solutions

The report generation toolkit didn't work after the vi was build to an application.exe

I write a VI using LabVIEW Report Generation Toolkit , it really works in the LabVIEW7.1 and 6.0 enviroment. but after the VI was build in to an application.exe, the LabVIEW Report Generation Toolkit didn't work even the application runs.
thanks for your help.

You might want to follow the procedure here:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/86256a47004e16d186256a84004cb883?OpenDocument
(If the URL doesn't work, you can search for NI document ID: 2B87TVI8)
Dan

Report generation toolkit does not work

Hello,
The report generation toolkit does not work.
It seems to point to the 'Generate Report Data Members.ctl'.
I suppose it has something to do with the wrong set of active X-controls ?
I work with Win 2000 and Office XP
How can i solve this problem ?
Thanks in advance !
Regards
Christine

Hello Julien,
Sorry for the late answer
I become a broken arrow, when openening the example Sample Report (Excel).vi
Searching further for the cause of the error it brings me to the sub vi tables.
Print screens in attachment
Regards
Christine
Attachments:
error Ni Reports.doc ‏67 KB

LabVIEW Report Generation Toolkit in the application does not work

I have LabVIEW7.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1, which was updated after installed. I made a VI in LabVIEW7.1 enviroment using the Report Generation Toolkit and it works very well. After the VI was build an application.exe and installed even in the same PC, the Report Generation Toolkit didn't work. Excel that should pops-up does not do anything.
the office i used is office xp. would you like to help me?
thank you very much.
Jing

When you build the application, you have to include as "Dynamic vi" in Source file tab the vi:
_Word Dynamic VIs.vi. from _wordsub.llb
_Excel Dynamic vis.vi from -Excelsub.llb
in the following library
...\National Instruments\LabVIEW 7.1\vi.lib\addons\_office\"
Refer to the following discussion thread
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=50650000000800000053460000&ECategory=LabVIEW.LabVIEW+General

Report generation toolkit: Avoid a separation of title and image at pagebreak in a work document.

I want to generate a report with the report generation toolkit in LV7.1.
In that report I use several report VIs to append text, titles and frontpanel images to a word document template (Office 2003). That works fine.
Depending on the size and text of my generated report, I have sometimes a problem with pagebreaks: A image is set to a new page if there is not enough space to place it on the old one. That’s ok. The text/title above the image is still on the old page. That's right, but I don’t want this. I know in Word you can use the paragraph formatting options to avoid a separation. But with the corresponding VI from the toolkit (word format paragraph (adv)) it seems not to work. With this VI you should have access to "indents and spacing" and to "line and page breaks". I always and only can change the "indents and spacing". En- or Disabling line or page breaks with this VI does not work, nothing changes in a word document.
Has anyone some suggestions or other solutions?
Thanks in advance!

Thanks for your input. You are right, that works and could be an alternative.
In the meantime I found a solution with creating my own activex vi instead of that from the toolkit as you can see in the attached image. Maybe this could help someone with similar problems...
Attachments:
KeepWithNext.JPG ‏46 KB

How to create a working link anchor in an EXCEL document with the report generation toolkit?

I am using the latest report generation toolkit and want to add links on the first worksheet pointing to the other worksheets in the same document.
I am using the "Append Hypertext Link Anchor to Report" VI. The links are created, but don't work when clicking them.
Question now is: How does a link to a cell on a different worksheet needs to look like?
It can not be that complicated but all variations I tried did not work and I could not find any information about this problem. So any help is appreciated!
Thanks and Regards,
Ingo
Solved!
Go to Solution.

Thanks, Brian, for your support! - It's working.
It's hard to understand why NI did not pass this parameter to the top of the call chain...
I also needed some time to understand the syntax of the string passed to the subaddress node:
The name of the worksheet needs to be framed by single quotation marks and the following cell address must preceeded by an exclamation point (!).
A working link pointing to cell "A1" of "Worksheet 1" looks like:
'Worksheet 1'!A1
Maybe also of interest: If you want to point the link to a worksheet inside the document itself, the parameter "address" (URL of link - href) can be left empty.
Thanks and Regards,
Ingo

Report generation toolkit 1.1.2 doesn't show up on the panel

I installed Report Generation Toolkit 1.1.2 together with the Labview 8.5. But when I looked into the function panel, it didn't show up. No Labview has been ever installed on this machine. However when I went to control panel "Programs and Features"-> National Instrument, it did show the "Report Generation Toolkit for Microsoft Office 1.1.2" there. So I guess it did install it, but how can I add them into the function panel. Btw, my system is Vista.

Hi lshi,
Glad to hear that reinstalling the Report Generation Toolkit resolved
the problem. To answer your question, the installer prompts for an
installation directory to allow users with multiple versions of LabVIEW
to select a version other than the latest.
Peter K.
National Instruments

Labview 2013 report generation toolkit word 2010 insert table problem

Hi,
I am currently evaluating LV2013 with respect to the report generation toolkit for use with word 2010. My Vi/program won't insert the correct table and gives me an error message. see below:-
Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table.vi->NI_Word.lvclass:Append Text Table to Report.vi->Word Table save.vi
I have since run the following word example.vi provided by NI within LV2013 office examples:- Growable table.vi. this gives me the same error!
Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table.vi->NI_Word.lvclass:Append Text Table to Report.vi->Growable table.vi
It would seem that regardless of my own Vi there is a fundamental problem in the office example vi.
I have found examples of a similar problem in LV2011/2012 but the work around code doesn't seem to match the LV2013 vi's code for a direct replacement.
Can anyone help/shed some light on this?
Thanks in advance,
Dan.

Because the upgrade of Word from 2007 to 2010 I needed to upgrade an existing application from LabVIEW 2009 to 2013. This didn't work because of the insert table error. I discovered that the problem is the vi called "Word_Insert_Table.vi" located in the ..Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\addons\_office\_wordsub.llb. There is a "Cut" command implemented, this command removes the created cell instead of clearing it. Therefore the table will be filled half and then returnes with an error. I have removed this command. I have posted the changed vi (LV 2013).
Attachments:
Word_Insert_Table.vi ‏30 KB

Report generation toolkit and signal express user step : problem of closing reference in "Stop" event

Hi all,
I'm trying to make a package of Vis to easily make Excel reports with Signal Express. I'm working on LabVIEW 8.2.1.
I'm using the report generation toolkit, so I build a .llb from my project which contains all the hierarchy of my steps, but also the hierarchy of dynamic VIs called.
I have made some steps, like "Open Workbook", "Write Data", etc.
My steps run well, excepts one step : "Close Workbook".
If my "Close Workbook" step is firing on "Run" Signal Express event, I have no error, so my reference is properly closed.
But if my "Close Workbook" step is firing on "Stop" Signal Express event, I have an error "1", from "Generate Report Objectrepository.vi".
I feel that I'm trying to use a reference which has been killed in the "Stop" step...
I would like to know what exactly do Signal Express on "Stop" event and why my close function does'nt run well.
Thanks,
Callahan

Hi Callahan,
SignalExpress (SE for short) does the following on the Stop event:
1. Takes the list of parameters that SE found on your VI's connector pane, and sets the values that the user set from the "Run LabVIEW VI" configuration page, if any.
2. Then tells the VI that SE is running the Stop event by setting the Enum found on your VI's front panel. This in turn should produce some boolean values telling your VI to execute the Stop case.
3. The VI is then run, with those values and states.
4. SE checks to see if any errors where returned.
5. Since this is the Stop event, SE releases the reference to the VI which it possesses.
Questions for you would be, is the reference to your Workbook linked to a control on your connector pane, or held in a uninitialized Shift Register. If it's held in a Shift Register, SE would not be aware of it, and would not be able to affect that reference.
Hope that helps. Feel free to post your LLB if it doesn't.
Phil

LabVIEW VI with Report Generation Toolkit elements in a TestStand sequence does not run with a LabVIEW 8.5 Run-Time Engine

Hi all,
I am using LabVIEW 8.5.1 and TestStand 4.1. I have done a TestStand sequence with a VI in it, which uses Report Generation Toolkit elements. On my machine I am using LabVIEW and TestStand with a Development System license. On the other machine I am using TestStand with a Base Deployment license and I have chosen the LabVIEW 8.5 Run-Time Engine in the Adapter Configuration. Everything is running well except of this VI with Report Generation Toolkit elements. The error message is showing that the VI is not executable. It works well only after I have installed LabVIEW with an Evaluation license and chosen LabVIEW 8.5 Development System in the Adapter Configuration.
I have found other posts and a document in the KnowledgeBase with a similar problem: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402?OpenDocument But I am not using EXE files in my sequence, so I don't know how to solve mine. Anybody has an idea?
Solved!
Go to Solution.

Hello guys,
thank you very much for your answers!
@Ruediger:
I tried to follow the instruction for Method 2 in the mentioned document: http://digital.ni.com/public.nsf/allkb/F3DC40A6E3F3B25B862570AD005D1D3D?OpenDocument, but the steps on my machine are different starting from step 4. After I click "Continue..." in step 3, I dont get a window, the system just makes a new folder with the same VI.
To be honest, I am new to LabVIEW and have some difficulties at this time. What I understood from your reply is, that I need to make a LLB-File, where the files from Report Generation Toolkit are in!?
@GovBob:
I was following the instruction in the document: http://digital.ni.com/public.nsf/allkb/9E00E7EFE0635E678625734600779EFE, but it wasnt working. Can you please tell me how I can check if the VI Server is installed and running on the machine?
I am using LabVIEW 8.5.1 and TestStand 4.1 on my machine, on the deploy machine there is TestStand 4.1.1. The version of my Report Generation Toolkit is 1.1.2.
Kind regards, Roman

Report Generation Toolkit Evaluation doesn't work

Similar Messages

Maybe you are looking for