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

Similar Messages

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

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.

REPORT GENERATION TOOLKIT AND EXCEL

i have a problem with report generation toolkit and excel
the problem is:
i must read & write from a excel worksheet when this is open but when i using the report generation the worksheet is open another time
have some solution for this problem?
sorry for my english

You need to close Exel when before your VI is running. Excel can not have two instances running at the same time.
Joe

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

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

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

Running macro on Table using Report Generation Toolkit and Office 2003 Incompatible!!!!!!!

Hi,
I am using some functions under the Report Generation toolkit (LabView 7.1). We recently updated our test PCs from Office 2000 to 2003. The "WORD IMPORT MODULE.VI" returns error code -41113 when used with Word 2003. No problem on Word 2000.
In fact even the example VI available under Find Examples - Run Macro on Word Table fails and returns error code -41113 when "WORD IMPORT MODULE.VI" is called on Word 2003. Word 2000 is OK.
Any one faced this problem???? Any solution to this problem??
I would greatly appreciate your feedback / suggestions.
Thanks,
Mim

darren,
thanks for your reply.
After checking the the property "Trust access to Visual Basic Project" , I get the following error message:
Exception occured in Microsoft Word, Unable to run the specified macro. Help Path is C:\Program Files\Microsoft Office\OFFICE11\1033\wdmain11.chm and context 37401 in Word Run Macro.vi->SetFirstRowAsTableHeaderforWord(Macro).vi->Generate Report.vi
I can run the macro directly from Word.. no problem running macros in Excel dirently either. I get error message only when running macro from LabView. So, I doubt if it is an IT issue.
You don't have a problem with Word 2003 and Word Import Module.vi???
I am attaching my Vi-Report Generation.vi and the subvi. I would so much appreciate if you run ReportGenerate.vi on your PC and let me know if there is a problem.
Many Thanks for your help.
Mim
Attachments:
ReportGeneration.zip ‏75 KB

Report generation toolkit and column

Hello, i asked this question before, but this time i just needed some input..
I originally asked, if i am doing various experiment sets and say each sets takes in about 1000 data points, and i have to do 50 such experiments continously i wanted to know if there was a way of arranging the data so that for each experiment is written in a different column, so i have 50 different column. Instead of the current one column with 50000 data points.
I was kindly suggested various alternatives such as using arrays...now my querry is regarding something that i heard which involves Report Generation toolset.
If i was to get this toolset, with this make my life easier interms of sorting my data out into different columns? I ahve also been
told it will do all sorts of graphs and do pretty much everying thing falling short of making a cup of tea
Now has any one had any experience in this type of porblem? or do i have to stick with the array solution. Incidently the reason why i have a niggling problem with arrays is that my programme is stricly no limited to just 50000 data for some runs i can decide to take more data in one set then the orther so building an array becomes problematic.
Please let me know what you all think of this kind Regards
Mansoor

Hello Mansoor
If you want to write the data to an Excel spreadsheet there are several options available to you as well as the Report Generation Toolkit.
I have posted some links to help and advice on performing this action using the toolkit, but also using the file I/O vi's and using active X.
Have a look at these links and if you have any further questions please reply to this post.
Report Generation Toolkit User Manual
http://digital.ni.com/manuals.nsf/webAdvsearch/46334E8183C5360586256E3F00603DDB?OpenDocument&vid=niwc&node=132100_US
Report Generation Toolkit Tutorials
http://zone.ni.com/devzone/devzone.nsf/webcategories/A50386FBB21ECC1A86256AB7006C2E6C
File I/O information
http://zone.ni.com/devzone/devzone.nsf/webcategories/BC4E8ABB211CFE7F
86256A1F0062CEB2
Writing data to an Excel file example in the LabVIEW example finder at the following location: - �Communicating with External Applications -> ActiveX -> Excel -> Write Table to XL.vi�
Regards
Hannah
NI

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 and Office XP and 2K

Hello Everybody
I am having few problems with running executable using Report Generation Toolkit on machine with Office 2000, which was compiled and build on machine with Office XP (toolkit also XP).
There are many errors which pops up, but the very first one is that the "New Report.vi" can not open the existing Excel book.
Is there any trick, which allows machines with Office 2k to run application build with Office XP?
Thanks in advance.
Pawel

Hi Cin
Yes, that is correct. The reason why I ask was how to find a solution so both XP and 2k can work in the same time.
You are right that most of the features for XO and 2k are simmilar, but try to use XP to open w 2k workbook from excel, it will fail.
cheers
Pawel

Potential Bug with LabVIEW 2009, Report Generation Toolkit, and MS Office 2003

We have discovered an issue with the above listed software. Specifically this pertains to Print Report.vi in the Report Gen palette. Basically, we have discovered that with Office 2003 installed the VI will error out. We've been using it in an executable, and the executable physically fails (and asks us to report an error to Microsoft). With Office 2007 we don't have a problem. We've tried building the examples into executables, and those work because they are printing HTML reports.
Also, we have converted back to LabVIEW 8.6 and rebuilt the executable and installed and it works perfectly. Its on the combination of LabVIEW 2009 and Office 2003 that seems to fail.

yeah, we had seen that, and been told about it by another user. we tried, to no avail. we still have ended up having to migrate back to 8.6.1 to get the executable to run properly.

Report generation toolkit and Stand-Alone Application

I know this question has been posed many time already. I have been fighting this issue for a week now and I've exhaused all ideas I can think of.
I have an application that I moved to another PC. For the past year or so it has been running off of a machine that has LV installed (LV2010). The issue is none of the RGT VIs seem to be working. I know this is related to additional files that need to be included in the application, an believe me, I have tried, but nothing works. I have read through all the threads I can find related to this issue as well as documents and the LV Help.
--It is my understanding the the dynamic VIs for Excel and Word do not need to be included for LV versions higher than 8.2. But I tried anyway and nothing.
--I've added the folders LVClass and NIReport.llb folders to my project and "always included" in my application. Still nothing.
--I've tried adding NI_Excel.lvclass to my project as the instructions in the help say to do and included it into my application. Still zilch.
--I've tried different combinations of things to try and get this to work and I get the same result.
For some reason, the program cannot find the VIs it needs in order to generate the report. No errors are returned either from the application.
I should note that when I included the NI_Excel.lvclass to my application that the size of the program did not change. I thought this was strange. It appeared the files in the class did not get included since they were not greyed out; however, after including the NIReport.llb which contains this class, they did get included, but unfortunately this did not fix my issue.
One question I have is why do the files in the LVClass and NIReport.llb folders not appear in the Preview, but if you have "Use LabView 8.x file layout" under the Advanced page checked, they do? This should be unchecked I know, just curious as to what was witnessed.
I am hoping this is something simple that I have over-looked. I'm tired of beating my head into the wall. I appreciate any assistance you folks can give.
Thanks.
Reese, (former CLAD, future CLD)
Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home

Wayne.C wrote:
Mo,
The .exe created with the 8.x unchecked runs just fine. I did check and the .exe is larger due to the extra files inlcuded directly in the .exe vs the Data folder.
Yes, I noticed this as well.
Let me ask, if if the class libraries are in the dependencies, won't they be a part of the application? So why does it need to be included. NI_Excel.lvclass in in the dependencies.
Reese
Reese, (former CLAD, future CLD)
Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home

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

Report Generation Toolkit and Labview 8 ?

Similar Messages

Maybe you are looking for