Report generation VIs in Labview 6.1

Hello,
I am havinf problems with using Labview 6.1 VIs for report generations. The VIs provided by Labview are not executable! It seems as if they had internal errors, non fixed errors. Moreover, I am not able to open the diagram because it is password protected. Does someone know if there is any patch to fix this or the reason why these VIs don't work?
Thanks a lot!
Regards,
María

Hello Maria,
are you using the report Generation Toolkit for MS Office or the standard vis that LabVIEW provides for report generation?
If you use the Office toolkit, this may help:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/c8888a9a74e75c4786256cda00694a1e?OpenDocument
If not, this may also help:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/9acb175f6de483ae86256b2200776b8b?OpenDocument
In any case, WHAT I WOULD TRY FIRST is to do a Mass Compile of the folder where the report vis are located.
Here you can see what this does and how to perform it:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/654877e62a97b72986256c95006f9b24?OpenDocument
One last question...are you having trouble only
with executables or also during development?
Regards,
JorgeM.

Similar Messages

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

Report Generation toolkit for labview 2010

H All.
I'm looking to download the report generation toolkit for labview 2010. When I proceed to download the toolkit from the national instrumnets website, it says that i need to labview 2011 or later in order to install it.
Is there a version of this report generation toollkit for labview 2010 and can someone provide a link maybe??.
Thanks for reading.
Solved!
Go to Solution.

Try this: [Link removed, NI software downloads can be found on ni.com/downloads, the LabVIEW 2010 Report Generation Toolkit is available to customers with Standard Service Program here: http://joule.ni.com/nidu/cds/view/p/id/3247/lang/en, other customers may contact NI directly]
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

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

Difference in the appearance of HTML vs. Standard reports generated with the Report Generation VIs?

When I generate a "Standard Report" (to a printer or PDF) with the attached code, the output looks like this:
If I instead use the same code to generate an HTML report, the output looks like this:
Can anyone explain why the HTML output has had the extra spaces stripped out of it?
Is there anything I can do to prevent it from happening?
VI is attached (LV v11.0.1f2) but this is what it looks like...
Attachments:
Print Test.vi ‏47 KB

SteveBale wrote:
If you look at your html source the spaces are there. The problem is the way html is rendered it removes the spaces. You will either need to add in <pre> </pre> tags to tell the browser to include those spaces, or insert the string   which the browser interprets as a single space.
Regards,
Steve
OK, thanks. I guess I'll end up living with it the way that it is because
using either method seems to also have the side effect of causing the output to become double-spaced and
the only reasonable place to implement the change (so that it did not also impact the "standard report" output) would be within the report generation VIs and I'd rather not be modifying them.

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

Word report generation VIs are not found.

Hi,
I've installed LabVIEW 6.1 followed by installing Report Generatio Tool set, but I don't find word specific VIs and excel specific VIs on Function Palatte. Could u plz. let me know what I m missing there.
Regards
GNS

GNS,
Which version of the toolkit did you install?
Do you see the Report Generation Toolkit listed under the Add/Remove Programs in control panel?
If you have multiple versions of LabVIEW, check in which folder did the toolkit get installed.
Can you find word and excel llbs under ...\LabVIEW 6.1\vi.lib\addons\_office directory?
If these VIs didn't get installed, you should check the version (LabVIEW 6.1 needs toolkit version 1.0.1) and reinstall the toolkit.
If you do have these llbs, try to manually edit the palettes and add new subpalettes linked to these menu files:
LabVIEW 6.1\menus\default\excel.mnu and
LabVIEW 6.1\menus\default\word.mnu
Check out the following KnowledgeBases as well
"Palettes Not Populating" Error with the Report Generation Toolkit 1.0 for Microsoft Office and LabV...
Installing the Report Generation Toolkit on Multiple Versions of LabVIEW
Zvezdana S.
National Instruments

How can i build exe which includes report generation tools,in labview 2010

I hv made exe.
I hv appended template word file to NewReport.vi.
when I m executing application,It is nt generating report.
Tell me the solution...!

Try this: http://forums.ni.com/t5/LabVIEW/get-doc-report-generation-working-in-build-does-work-in-LV/td-p/1790...
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

Can't print to Epson TM-U590 Slip Printer from Report Generation Toolkit with LabVIEW 8.6.1

Hi all,
I have an application that uses the Report Generation Toolkit to print tickets to a docket printer. Usually this works fine - I have 8 existing installations where there are no problems
I'm currently installing the software at a new site that uses an Epson TM-U590 slip printer and I can't for the life of me get printing to work
Using a Standard Report, the Print Report.vi returns error -41002 which indicates it can't find the printer. I've opened up the VI using remote debugging and it does find the printer name correctly with the Query Available Printers.vi. It gets an error code -2147352567 from the Printout node, which then gets replaced with the -41002 error which is reported.
For historical reasons I'm still using LabVIEW 8.6.1 for this project. I'm considering moving to 2011 or 2012 but I've had reliability issues with other parts of the application after attempting to update to a newer LabVIEW version so I'd like to avoid that at this stage.
The application is running on a standard desktop PC with Windows 7. The slip printer works fine if I print to it from Notepad, and my application is happy to print to any other printer, just not the slip printer.
The slip printer is using the LPT port. Previously the docket printers I've used have been USB but I would expect the printer driver to hide this detail from the application...
Any ideas would be much appreciated
Cheers
Brett
Senior Software Development Engineer
Certified LabVIEW Architect and LabVIEW Champion
Solved!
Go to Solution.

I've managed to sort out the problem, thanks to this KB article: http://digital.ni.com/public.nsf/allkb/67D60209102E2161862568AC0074BF64
I'm now having the same issue with a Star docket printer (a TUP592), this time with another program developed in LabVIEW 2011.
As mentioned in the article, the problem is actually to do with the margin settings rather than the printer name, despite what the error message says
After some experimentation, I've gotten the Star printer to work by setting a large (>14cm) right margin. No idea why this is required as it seems to print right up to the right edge of the paper quite happily, but there you go.
So I haven't defintely fixed the original problem yet as I haven't gotten back to the site, but hopefully this will be of some help to someone else.
Cheers
Brett
Senior Software Development Engineer
Certified LabVIEW Architect and LabVIEW Champion

Report Generation Toolkit and Labview 8 ?

I currently have Labview 7.1 on my computer, and Labview 8. I have installed the Report generation Toolkit 1.1.1, but when I try to open several of the excel and word vi's in labview 8, I get the error that "constants wired to case structures were changed to a hidden control to maintain compatibility with labview 7.1 and earlier". And therefore the subvi's don't run. Labview 7.1 doesn't have the toolkit installed, and I've even tried uninstalling 7.1 but nothing works. How do I fix this? Relinking to subvi hasn't work because it is not offered on any of the errored vi's or subvi's. The broken wires are going into invoke node vi's, but I don't know how to fix them. It doesn't allow me to rewire them.

If you dont want to use it in LabView 7.1, Just make a mass compile with LabView8.0 on the directory of you package.
It could solve a lots of that kind of problem.
Be sure that you do net need it with your previous version.
Benoit
Benoit Séguin
Software Designer

When i am trying to create a report(using graph) in Word97 using Report generation Toolkit from Labview it's giving error in word import Module.vi that no such interface is supported could anyone help me out to solve this problem

Word import Module.vi is trying to call Vb project and VB components thru active X controls when it's trying to call Vb components it's giving the error no such interface found..I am using Labview 6,MSoffice97,Graph8

Hi Adam,
It seems that there have been a couple other instances of the same error occurring and the problem is a conflict that occurs with the Office 97 only. Somehow the MS Office type library has been modified and this is causing incompatibilities with MS Office 97. Have you installed any other application on top of MS Office that plugs into MS Office tools – Adobe Acrobat, Visio, Reflection?? If so, you will want to see about uninstalling or reinstalling those utilities and then reinstalling Office 97 to restore the original MS Office 97 type library.
Also, if you have a newer version of MS Office, I would highly recommend upgrading your computer. It seems that this problem is only with Office 97 and later versions of Office do not have this issue.
Thanks again for bringing this question up.
Kileen

How can I change the position of the page footer when using the report generation functions of LabView 6.1.

At present my page footer is printing too far up from the bottom of the page. I have been unable to find a property that enables the position to be changed.

Use the Set Report Margin.vi to set the bottom margin to something less than the default 1. I got a standard report to print a footer .2 inches from the bottom of the paper.

Report generation toolkit (1.1.2) and 8.5

I am not as crazy as I thought!
I wrote a program today that collects data from excel reports in many directories using cell names and it worked well. Unitl I saved it. I had been saving the sub vi's, but when I went to close them I got a message about unsaved changes and I guess I clicked to save the changes today. The program never worked the same again. I would get errors like 41106 and 41110 at random (problems with excel not opening and other stuff). I tried adding waits which slowed everything down and worked mostly. But the only way to not drop data and get errors was to have a copy of excel open while getting my data.
Well I just uninstalled/reinstalled the toolkit and rebuilt the vi that was having problems with the fresh install and everything is great again. So my question is why does the toolkit have problems when I save it in 8.5? The warning does say that the vi's are from 7.1 and I cant find any updates so I am hoping this is the latest version that came with my 8.5 suite.

Hi Bryan,
There should not be a problem with saving the VIs from the Report Generation toolkit in LabVIEW 8.5. I have checked the readme files to make sure but RGT 1.1.2 should work with any version of LabVIEW later than 7.0. However, the readme does discuss an specific upgrade issue. It says if you previously created VIs that use the built-in Report Generation VIs in LabVIEW Professional, Full, or Base packages or VIs from a previous version of the Report Generation Toolkit, installing the Report Generation Toolkit 1.1.2 might break the VIs you created. If the VIs you created contain any of the following VIs, edit them so they are compatible with the Report Generation Toolkit 1.1.2.
Append Front Panel Image to Report VI—The Image Format input of the LabVIEW 6.1 version of this VI is a different enumerated type than the current toolkit version. Right-click the input and select Create»Control or Create»Constant from the shortcut menu to create a compatible control or constant.
Append Table to Report VI—The connector pane position of the show grid lines input changed from the Report Generation Toolkit 1.0.1 version of the VI. Reconnect the original wire to the new input location.
Get Report Settings VI—The cluster order of the font settings input changed from the Report Generation Toolkit 1.0.1 version of the VI. Right-click the output and select Create»Indicator from the shortcut menu to create a compatible indicator.
Report Express VI—If a VI includes the LabVIEW built-in version of the Report Express VI on the block diagram, the VI breaks after you install the Report Generation Toolkit 1.1.2. Double-click the Report Express VI to launch its configuration dialog box, then click the OK button. Reconnect all wires to the Report Express VI.
You might need to relink the following subVIs after installation because the connector panes changed in the Report Generation Toolkit 1.1.2. Right-click the VIs and select Relink to SubVI.
New Report
Dispose Report
Append Front Panel Image to Report
Append Hypertext Link Anchor to Report
Append File to Report
Append Horizontal Line to Report
Set Report Font
One thing that might have happened is if you had created the program in an earlier version of the toolkit, then saved it in the new version of the toolkit, maybe some of the upgrade issues regarding the VIs listed aboved cause LabVIEW to start giving you errors. Also, which version of excel are you using? After you re-did the VI program, have you tried to save it again and see if the same problem occurs?
Carla
National Instruments
Applications Engineer

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

Report generation VIs in Labview 6.1

Similar Messages

Maybe you are looking for