Report generation broken VIs in LV2009

Hi,
C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\Utility\NIReport llb has 2 VIS "Get modified data" and "Set modified data" which are used by Report generation tool kit .
I installed LV2009 in which "Get modified data" and "Set modified data" are not present. When i installed report generation toolkit then, the report generation VIs in "LV2009\vi.lib\addons\_office" VIs are broken because they are search for above mentioned VIs.
Report generation 1.1.1 is what i am using.
Please suggest me a solution.
Regards,
Muthuraman S
Message Edited by Muthuraman on 10-29-2009 01:10 AM
Regards,
Muthuraman

yes might be, why don't you use the report generation toolkit along with the developer suite.
because same thing happened to me when i installed Report generation 1.1.1 with LabVIEW 8.6, then installed Version 1.1.2 which was along with developer suite.
Regards
VIsuman

Similar Messages

Report Generation broken after deployment - Excel Set Cell Color and Border.vi

Upon deployment, the Excel Set Cell Color and Border.vi became broken. After installing LV2010 SP1 to view the VIs in the deployment, I noticed that in the second case structure where the code draws the border using the BorderAround invoke node, there is an extra variant input parameter named 'Parameters'. Upon right-clicking, an option to 'Relink Invoke Node' appeared and after selecting this, the extra input disappeared and the VI was no longer broken.
Why does "Relink Invoke Node" appear? How do I create a deployment with this issue? Has anybody else experienced this? Why is the TestStand deployment so buggy?

Hi Ching-Hwa,
I have set up a test deployment here where I am deploying a workspace that contains a sequence file. This sequence file has a LabVIEW Action Step calling a VI that opens a new Excel file and simply calls the Excel Set Cell Color and Border VI. After deploying this, both the VI and my test sequence ran on the deployment machine without error. Therefore, I do have some more questions to more accurately reproduce what you are seeing.
First, what operating systems are you developing on and deploying to? Also, what license do you have for TestStand on the machine you are deploying to? If you have a development version, can you manually take the sequence file and VI to this machine and run it? I know you now have LabVIEW 2010 SP1 on your development machine, but if you have the development version of TestStand as well, it would be interesting to see if you copy the files over if you still see this behavior. Are you including the TestStand Engine in the deployment?
Can you open a blank VI on the deployment machine and add the Excel Set Cell Color and Border VI? It would also be interesting to see if this is not a product of the deployment, but rather an issue with something on the deployment machine itself. What version of the Report Generation Toolkit do you have on each machine? Also, what versions of Excel are you using on the development and deployment machine? Again, it would be helpful for me to know exactly what versions you have installed on both the development and deployment machines so that I can reproduce this as accurately as possible.
One last thing to try, too, would be to try deploying the VI by itself just to see if it also has the same behavior. Do you have the Application Builder in LabVIEW? If so, could you also try building an executable from the VI, create an installer, and deploy this to the deployment machine?
In regards to the "freezing" of code by removing the block diagrams, I do not believe this will be a proper work around in this case. While this removes the block diagram from actually being deployed along with the VI and restricts users from editing the code on the deployment machine, if something is getting changed in the compiled code upon deployment, this will not stop this from happening. This option is available more as a memory option to lower the size of the deployment as well as prohibit any users on the development machine from editing the block diagram themselves.
Thanks, Ching-Hwa! I look forward to your response so that I can continue trying to reproduce this issue. Have a great day!
Taylor G.
Product Support Engineer
National Instruments
www.ni.com/support

Error Showing While Using Report Generation ToolKit VIs

Hi All,
           When I use report generation VIs Like Excel Easy Tables its showing following errors and i am not able to contiune using the same,
C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\utility\NIReport.llb\Set Report Font.vi
    - LabVIEW 8.0 changed a constant that was wired to a Case structure to a hidden control to maintain compatibility with LabVIEW 7.1 and earlier.
    - LabVIEW 8.0 changed a constant that was wired to a Case structure to a hidden control to maintain compatibility with LabVIEW 7.1 and earlier.
what might be the issue, i am using LabVIEW 8.2

Hi,
In
LabVIEW 7.1 and earlier, subVIs could be kept in memory by wiring a
constant to a Case structure and placing the subVI in a case that would
not be executed. For example, you could wire a True constant to the
Case structure and place a subVI in the False case of the Case
structure, and LabVIEW would load the subVI along with the calling VI.
However, from LabVIEW 8.0 onwards, the case structure is optimized to remove code that is not going to be executed. Changing the
constant to a control ensures that this VI behaves as it did in LabVIEW
7.1 and earlier. If the intent is not to keep the subVIs in memory, you
can change this control back to a constant by right-clicking the
control and selecting 'Change to Constant' from the shortcut menu. The
proper way to keep a subVI in memory without calling it is to use a
Static VI Reference.
Good Luck!
Warm regards,
Karunya R
National Instruments
Applications Engineer

Old Report Generation Toolkit VIs

I have some old VIs I'm modifying and they, themselves, use VIs that used to be in the report generation toolkit but no longer are (Generate Report Get Data to Modify.vi, Generate Report Get Data.vi, show table lines.vi, etc...there are many more). I can grab an old library that I have on another PC that includes these VIs, but then that causes all sorts of conflicts. I have seen lots of things posted that are somewhat like this but no viable solution. Does anyone have one, so that I can load the VIs and not have to redo any code?
CLA, LabVIEW Versions 2010-2013

for(imstuck) wrote:
I have some old VIs I'm modifying and they, themselves, use VIs that used to be in the report generation toolkit but no longer are (Generate Report Get Data to Modify.vi, Generate Report Get Data.vi, show table lines.vi, etc...there are many more). I can grab an old library that I have on another PC that includes these VIs, but then that causes all sorts of conflicts. I have seen lots of things posted that are somewhat like this but no viable solution. Does anyone have one, so that I can load the VIs and not have to redo any code?
I believe that is yet anothe manifestation of the issue I posted about in this thread where using VI's that are not on the palettes, can sneak up and bite you when LV gets updated.
In the case of the DB and report gen tool kit, the first version re-written in LVOOP did not expose any methods to get at any of the classes agregated by the class (how is that for OOP speach?).
Latter version of those tool kits exposed the ref to the more advanced functions so first make sure you have the lateset and greaset version of the tool kits.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Report Generation Toolkit 1.01 and broken arrow

Hi,
I desperately need help because I need to build my application tomorrow morning for our production department and have trouble with the report toolkit.
I am aware of your knowledge base entry regarding this problem. I already deinstalled and reinstalled the toolkit (version 1.0.1 for LV 6), and I checked the windows registry entries. Still, after mass-compile, the report generation toolkit VIs are not executable (broken arrow, invalid property node). I have LabVIEW 6.02, 7.0 and 7.1 on my computer and I am using the report generation toolkit version 1.0.1 with LabVIEW 6.02 and version 1.1 with LabVIEW 7.1. The application that I need to build is written in LabVIEW 6.02. What else can I do to get rid of the broken arro
ws?
Thanks in advance for your fast answer....
Gabs

Hi,
the problem is the following: during the build error 1003 occures at ....\internal.llb\Word_New_Page.vi. Possible Reasons: LabVIEW: The VI is not executable. When I open my main VI, I see no broken arrow. When I force a mass-compile (Strg+Shift+Run button), the broken arrow appears suddenly. I can then see the following error message: Word Easy Text.vi is broken because Word Format Text.vi is broken because the Property Node Range\Style calls an invalid property. Actually, the property nodes in these VIs have NO properties and the invoke nodes NO methods.
I know now that this is due to the fact that I need to build this application for a computer on which Word97 is running, so I installed the Report Generation Toolkit for Word97. But - on my developme
nt computer where LabVIEW is installed Office XP is running, not Office97. If I install the Report Generation Toolkit for OfficeXP, no error occurs during the build, but the executable does not run properly on the target computer (when calling Word97).
Question for NI: How am I supposed to build an executable using Microsoft Word Report Generation Functions if the target computer has Word97 installed but the development computer has WordXP installed???
Please help,
thanks,
Gabs

Report Generation Toolkit on Vista and Office 2007

Hi,
I am trying to install Report Generation Toolkit 1.1.2 on LabVIEW 8.5 on a computer with Vista Business and Microsoft Office 2007.
The installation is starting, but I am receiving a message saying that "Microsoft Office 2000 or later is not detected on the computer"
The installation stops and the toolkit is not installed.
What can I do ?
Tom

Tom SAVU wrote:
Hi,
I am trying to install Report Generation Toolkit 1.1.2 on LabVIEW 8.5 on a computer with Vista Business and Microsoft Office 2007.
The installation is starting, but I am receiving a message saying that "Microsoft Office 2000 or later is not detected on the computer"
The installation stops and the toolkit is not installed.
What can I do ?
Tom
The Report Generation Toolkit does probably not support Office 2007 yet. This is because the Office ActiveX interface used to change with each version and the Report Generation Toolkit comes with specific libraries for each of the Office versions it supports. With the wrong office version the Report Generation Toolkit VIs are normally broken and can't run without some more or less involved modifications.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

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

Problems creating a web service that uses the report generation toolkit

Hi,
Im trying to develop a web service using labview 2013.
I create a html form that is correctly communicating with my labview method and part of the web service functionality is to create a report from the data obtained in the html form published.
I realized that using the report generation toolkit inside of the web service method the server cannot generate a report. ( If I run the same Vi before publishing the web service it works on the server but it doesnt work after I deploy it)
I thought that maybe Im unable to use the report generation toolkit VIs inside of the web service because Im not incluiding the (dynamic VIs labview uses when they run), I tried to add the excel dynamic library to the proyect but with no success.
I also tried to use VI SERVER to call a VI that generates the report using the report generation toolkit in the method that runs when the web service is call but it doesnt work either.
How can I deploy a web service able to use the report generation toolkit ?, how can I deploy a web service able to use VI server ?
Any help is really appreciated.
Erwin Franz
Erlab

The issue you are running into is actually a limitation intended by Microsoft. They don't want windows services to be able to call into the ActiveX interface for Microsoft Office for security reasons. If you are deploying your web service to the NI Application Web Server on Windows you will run into this problem since the web server is a Windows Service.
While I haven't tested this, you may be able to work around this by packaging your Web service with a LabVIEW EXE rather than deploying to the NI Application Web server.
Mark
LabVIEW R&D

Flash to iPhone and Report Generation

Is it possible for an iPhone app created through Adobe Flash Professional to save an image to the Photo application?
Is it possible also to send an email with an attachment?

KRAZE4LV wrote:Each files I reduce twice using each excel file
Instead of running the VI twice, why not change your decimation factor to 100 (instead of 10)?
I don't know what your reports are supposed to look like, so it's kind of hard to tell you what to do with the report generation toolkit VIs. All I can tell from your description is you need to create a report of Word type. I'm guessing from there you would want the Append Table To Report.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

LabView database connectivity toolkit 1.0.1 compatibility with MS-ACCESS 2010 / Labview report generation toolkit for Office 1.1.3 compatibility with Office 2010

In the very near future we will be forced to upgrade to Office 2010 Company wide and I am a little concerned with some of our older test platforms that have applications built in LabView 8.2.1. These applications save data to MS-ACCESS 2000 databases using the LabView database connectivity toolkit 1.0.1. Office 2003 is also loaded on these test platforms with all test reports generated using the LabView report generation toolkit for Office 1.1.3.
I have not gotten my hands on a copy of Office 2010 yet to see if there will be any compatibility issues. Does anyone have any experience in this area?

The MS-Access part is fairly well isolated through the ADO interface LabVIEW uses. The only possible problems there IMHO are difficulties with possible Acess compatibilities itself such as an example, SQL statement you may have invoked directly through the ADO interface. Maybe you did use a depreciated command back then that has since been removed. As long as the only thing you do are simple INSERT and SELECT statements only, I would expect it to just keep working.
The Report Generation interface is a different beast. Microsoft manages to change the Automation interface with every version of office in a way that strongly binding applications like LabVIEW break on. There is no good way around that except not changing those methods, but that is a cause that has been lost already. You will certainly have to verify the version dependant Report Generation API VIs to still work with Office 2010 and most likely you will have to make some changes to those VIs to make them work again with the modified ActiveX interface of Office 2010. Note, that I have no experience with porting report generation to Office 2010 but I have had some headaches from porting that between Office 97, 2000, 2003, and 2007.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Report generation and office versions

I have developed an application which uses the excell report generation features. I have Office 2007 on my pc with LV 8.51 and report generation addon 1.1.2. I wand to distribute (build) the application to users with office 2000. What steps need to be done. Do I need 2 different builds, will one build work? How do I specify which version of the office gets linked, is this dynamic?
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Hi Paul.
Thanks for the reply.
When building applications with Report Generation Toolkit VIs, you must complete the following additional steps:
• From the Source Files tab of the Build Application or Shared Library (DLL) dialog box, click the Add Dynamic VI button to
add the following two VIs to the application:
– _Excel Dynamic VIs.vi in vi.lib\addons\_office\_exclsub.llb
– _Word Dynamic VIs.vi in vi.lib\addons\_office\_wordsub.llb
Note, you'll need to add the VI's for both versions. You may need to re-name the vi.lib, because they'll have the same name (i think) but the references etc for different office versions do change and hence we you need to call different vi's.
• If the application you are building contains the MS Office Report Express VI, you must add any Word or Excel templates that you use to the built application. From the Source Files tab, click the Add Support File button to add the template files to the application. By default, the custom destination for the templates is the same as the path that appears in the Destination directory field on the Target tab with a data subdirectory appended. Do not change the custom destination for the files you add.
For example, if you are using the basic Excel template with the MS Office Report Express VI, add MSOffice_RGT_Template.xlt to the application. The basic template files are located in the
templates\Report directory.
Hope this explains it a little better,
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Report Generation VIs

Can VIs on the "Report Generation" palette in LV 8.6 be used or do they require that an additional utility be purchased?
Thanks,
Chuck M.
Solved!
Go to Solution.

Good Afternoon Chuck,
The NI LabVIEW Report Generation Toolkit for Microsoft Office is an additional package that needs to be purchased and activated before being used. Seeing the "Report Generation" palette and sub-VIs on your Functions palette simply means that the toolkit is installed; it does not guarantee that you can use them.
To confirm that the Report Generation Toolkit is activated (and useable), open NI License Manager, navigate to the Toolkits branch under your version of LabVIEW, and confirm that "Report Generation Toolkit for Microsoft Office 1.1.3" has a green box to the left of it.
If the box to the left of the name is not green, it means that particular product is not fully activated. To activate, right-click the name, and click Activate. Follow the on-screen instructions to activate. If you believe that you have purchased this Toolkit and are unable to activate it, please go to www.ni.com/ask to create a phone Service Request. An Applications Engineer will help you activate your product.
Regards,
Charlie Piazza
Staff Product Support Engineer, RF
National Instruments

Report generation vis are not running in exe

HI
Im using report generation vis for create a excel report.Its not working in exe.Even i included the Nireport.llb in
(C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility)to my project.wat to do?
kavi
Solved!
Go to Solution.

Hi kavi,
did you get some warnings while building the application?
See this link:
http://digital.ni.com/public.nsf/allkb/2AE85CF95217E60786257540000D818C
Mike

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

Generate report using Word Report Generation VIs error

When I Generate report using Word Report Generation VIs ,the error is generated.
This is my Vi
can somebody tell the error reason?
The attaché is Vi (one is 2011,other is 8.6)
Attachments:
report-8.6.vi ‏16 KB
report2.vi ‏33 KB
template.doc ‏40 KB

Hi Ben64
Thank you! The problem is solved.
BUT when I use the Word Easy Graph vi ,the result is
I want the Graph (curve),like as:
How Can I do get the picture.
I have other problem. I want to get default name for the new word file.
liang

Report generation broken VIs in LV2009

Similar Messages

Maybe you are looking for