Save the report that VI of report generation toolkit is broken

Hi all

I created a journal vi data, using report generation tools. He works first and then I copied the vi to another folder and tried to run but ended up with a broken vi.  The error occurs in the Save report vi of report generation package.   Please see vi and captures screen attached. I'm sure that if you run the vi, it might work on your machine, but will not work on mine. That's why I find it cable. Has anyone seen this kind of problem before?

Hi all

I spoke with an application OR engineer and we have tried to compile mass of Labview on the particular folder containing the VI.

Tools---> Advanced---> massive compilation.  This corrects the problem.

Thank you

Tags: NI Software

Similar Questions

  • Insert symbol in word doc using the report generation toolkit

    I'm trying to insert a graduation or a brand of corss the word doc by reading the bookmark. To enter a value, I used a control of the chain. But I have been unable to enter these symbols. I tried to make the insertion of an image, but it is to insert the image but don't replace do not bookmark. Please help me with this!

    ben64 wrote:

    Maybe these symbols are not included in the character set used by Word. Do you have something or nothing, is there an error message?

    Ben64

    Here is an example of what I said:

    I need to insert the check mark, set the font for report to Wingdings (restore the default font after). If I don't do this the character ü is written (0252 default font character).

    Ben64

  • Set the position of the cursor in the text added (to make the part of the text in index) in WORD using Report Generation Toolkit

    I would like to generate a report in WORD using the report generation toolkit.

    Whenever a text is added to the report, the program should put part of the text index. The problem I am facing with is to set the cursor position in the current location of the text.

    Any suggestions?

    Hello!
    I think that's what you wanted (see attachment).

    First, you must set position for each loop, so after adding the table, your cursor index need to increase the number of added characters. That's why I have included the text of the report, Append - to get the position of the cursor at the end.

    Indexing begins with 0, so you need to set the 3 and 7.

    Hope you get what I mean

  • The report generation tool must Office?

    Quick question: the Report Generation Toolkit (V1.1.3 for LV 8.6) should Microsoft Office installed to be able to create Word documents?

    I have a need to create reports, preferably in Word format, but the target computer cannot have the reader on your computer, office.

    Yes, you need office.

  • Report Generation Toolkit missing VI

    LabVIEW version 8.6.1

    Report Generation Toolkit 1.13

    I just started work on an ongoing project that others have contributed to during some time.  (This is why the project being in older versions of LabVIEW)

    On my PC, apparently miss me VI "Word get ActiveX References.vi"

    I have the version 1.13 of the installed tool, just like all other machines running this code performs.  But my word.llb only contains VI

    I tried to copy just that VI in the .llb the VI is then found by the application.  But is not executable due to this error: this VI is related to a library that does not include the VI. The VI may have been removed from the library. ' Add the VI to the library or select file "unplug library.

    I also tried to replace my C:\Program NIUninstaller Instruments\LabVIEW all 8.6\vi.lib\addons\_office\ the directory with the files from a PC that worked.  Yet once, I get the same error as above.

    I tried to do a repair on my installation of the box tool.  But as far as I know, it did nothing.

    I also tried just reinstalling the Toolbox.  But since that it has been already installed, it did nothing.  I would hesitate to uninstall and reinstall the Toolbox for fear of breaking all my 8.6 projects, as well as perhaps my 2009 projects.  I don't think that he messes with my 2009 installation.  But I know the order in which things are installed can be critical in the system with several versions.  I don't know if this applies to tool boxes or not.

    This PC also has a LV 2009 SP1 installation, and this version also has the Report Generation Toolkit installed. (even if it is a different revision of the Toolbox as 1.13)

    I know that in the past, several versions of this toolbox were not compatible, which means that a single version of LabVIEW installed might have a job Report Generation Toolkit installed.  But I have been in agreement that it was no longer a problem.  Although it may not be a coincidence that none of the other boxes development runs this code are not installed LV 2009 have.

    Anyone who has encountered a similar problem and found a solution?

    Thank you.

    Before that we unified the version numbers of LabVIEW and toolkit (in 2009), there are cases where it has not changed the version number in the registry for one reason or another on a minor update.  So very well may have installed 1.1.4 and it can still say 1.1.3.  However, assuming that 1.1.4 has been installed, I can't imagine any reason why Word get ActiveX References.vi wouldn't be here.  VI lives at vi.lib\addons\_office\word.llb, so after installation from 1.1.4 to your folder of LabVIEW 8.6, check that the VI is actually there.

    D

  • report generation toolkit VI error when running EXE

    A VI in the Report Generation Toolkit (version 1.1.2), Excel find Application Directory.vi, will not work correctly when you run an EXE file.  'Current VI course' block returns the path of the ongoing EXE rather than the path of the Application Directory VI find Excel.  (This would be true for Word find Application Directory.vi.)

    -Joel

    Have you had a look at this knowledge base article? The error is due to exclusion of all dynamics VI.

    Gregory C.

  • Report Generation Toolkit, production of the 2147417842 error, "The application called an interface that was marshalled for a different thread."

    Hello world

    I have an application that stores data in an Excel worksheet by using the report generation tool.  My VI have worked well in the past using Excel XP, but since I have upgraded to Excel 2007, I get COM errors like this:

    "2147417842 error occurred while the application called an interface that was marshalled for a different thread. in Excel_Insert_Text.vi', this is the exact wording, even with the odd punctuation and capitalization.

    The first occurrence of the error is not determined.  Sometimes, to the record 10 sessions, involving a new .xls file, may occur before this error.  Once this error occurs, I must leave LabVIEW to solve.  If I try to do something with Excel, I still get this error, even if sometimes it comes out different source Excel_Open.VI is another.

    These screw logging worked fine until upgrading to Excel 2007.  I checked and I have been using a very old version of the report generation tool, v1.0.1.  I read the documentation and had a big sigh of relief when I realized that I needed to upgrade to v1.1.2 for Excel 2007 help.  However, even after the upgrade, I still get the same errors.  I'm using LabVIEW 8.0.1 and I also build these screws in an application.   The error occurs in the application built both in the IDE of LabVIEW.  Anyone out there have any idea what I can do to fix this?  I google a bit and discovered it is a COM error, but I can't find any reference to the report generation tool specifically.

    Thank you

    Phil

    I think that suits him!

    Here's what I did: I left privileged execution environment level upper VI as "as the appellant.  I tried the "user interface" configuration, but it seemed to slow down considerably the program.

    Then, I found each sub - VI, calling the report generation tool and define the environment for running favorite "user interface".  All the errors went away, and the program is much happier now.

    Big assumption on what a Christian, thank you!

  • Method of Report.Save, the report has been made in a new path, but why is the empty file?

    Hallo,

    I have a problem to save the report file in a new way.

    In my code, I used the Runstate.Report.Save(newpath, overwrite, 0) method to save the report.

    And after the excution of the test, I can find the file of report in the right place, but if I open it, it's empty, I mean, there's nothing in this report.

    Someone has an idea? Where is the problem? And what I could do?

    Thank you!

    Cabio

    Hi Cabio,

    Before answering your question, I would like to let you know that you can configure the path to the report file in the report file path tab report options.  You can choose from several options, including by specifying an expression that is customized for the report path.  This will allow you to customize where the report is saved without changing code.

    If this isn't meeting your needs, the problem you're likely to have is that you access report until the report is actually produced.  To access the report object after it has been populated, replace the ProcessCleanup callback, which runs after the report has been generated.  (see the example of navigation PreUUTCallback for an example of substitution of a reminder.

    Note: if you use TestStand 2012, this method will not work unless you configure Report Builder for not using a new thread.  You can configure this option in the treatment of dialogue by selecting the checkbox options more results.  If you do not want to use a new thread, you can access the report by changing the sequence of AddUUTReportAndSave in ReportGen_ATML.

  • How to create an anchor to the working link in an EXCEL document with the report generation tool?

    I use the last report generation toolkit and add links on the first worksheet pointing to the other worksheets in the same document.

    I use the VI "Append hypertext link anchor to report." The links are created, but do not work when you click on them.

    Question now is: how a link to a cell in a different spreadsheet should look like?

    It can't be that complicated but I tried all the variations did not work and I have found no information on this issue. So any help is appreciated!

    Thank you and best regards,

    Ingo

    Go down to NI_ReportGenerationToolkit.lvib:Excel_Insert_Link.vi on hyperlinks invoke node you need to wire the node sub-address to the location of the cell to bind to.

  • Cannot print on the Epson TM - U590 Slip printer Report Generation Toolkit with LabVIEW 8.6.1

    Hi all

    I have an application that uses the report generation tool to print tickets for a printer file.  Usually, it works very well - I 8 existing facilities where there is no problem

    I install the software on a new site that uses a printer Epson TM-U590 slip currently and I can't for the life of get me printing to work

    Using a Standard report, the Print Report.vi returns error-41002, indicating it does not find the printer.  I opened the VI using the remote debugging and it does not find the name of the printer properly with the available query Printers.vi.  It gets an error-2147352567 code starting from the printed node, which is then replaced by the de-41002 error that is reported.

    For historical reasons, I always use LabVIEW 8.6.1 for this project.  I plan to spend in 2011 or 2012, but I had some reliability problems with the other parts of the application after trying to upgrade to a new version of LabVIEW, so I would avoid it at this point.

    The application runs on a standard desktop with Windows 7.  The slip printer works fine if I print from Notepad, and my request is happy to print to any other printer, just don't slip printer.

    The slip printer using the LPT port.  Previously, printers of the folder that I used were USB but I expect the printer driver to hide the details of the application...

    Any ideas would be very appreciated

    See you soon

    Brett

    I managed to solve the problem, thanks to this article: http://digital.ni.com/public.nsf/allkb/67D60209102E2161862568AC0074BF64

    I now have the same problem with a folder of Star printer (a TUP592), this time with another program developed in LabVIEW 2011.

    As mentioned in the article, the problem is in fact to do with margin settings rather than the name of the printer, despite what says the error message

    After some tests, I received the Star printer to work by setting a large (> 14cm) right margin.  No idea why this is necessary because it seems quite happily print to the right edge of the paper, but there you go.

    So I don't have defintely solved the original problem yet, as I've not had back on the site, but I hope that it will be useful to someone else.

    See you soon

    Brett

  • How to display the drop-down list box in MS excel by using labview report generation toolkit? pleasepost code block diagram?

    How to display the drop-down list box in MS excel by using labview report generation toolkit? Please post the block diagram of the code so that I can able to generate from the drop-down list box in excel with the menu drop-down...

    Like this. (edition, use the reference forms instead of the reference to the worksheet)

    Ben64

  • How to use the report generation tool to get a list of bookmarks in a Word template

    I'm working on a project where I need to use the report generation tool to fill a fairly long Word template. MS Office report Express VI can have entries for a maximum of 17 bookmarks that is not close enough to what I need to do.

    I wonder if there is a way to use the lower level screws report generation to read the word template and return a list of the names of bookmark in the form of a table 1 d of string. The dialog box that allows you to implement the Express VI has this ability, but I'm not finding a way to scan the document programmatically.

    I'm sure I can't be the first person to encounter this problem and I hope someone out there has found a good solution.

    Found the answer to this one that I was looking for the forums. Apparently, you can do this directly through everything in the VI report tool, but there is a VI in Wordsub.llb do that.

  • LV Report Generation Toolkit for Microsoft Office said "this VI or element belongs to a library that has expired or improperly licensed."

    I downloaded the LV Report Generation Toolkit for Microsoft Office for evaluation with LabVIEW 2010. Examples to help get a lot of errors, including "the Subvi is not executable. You must fix any errors in the Subvi before this can run VI. "and"this VI or element belongs to a library that has expired or improperly licensed. "

    I decided that I wanted to evaluate the Toolbox instead of putting an activation code during installation. Installation went well.

    How can I get the examples from this LV package to run so that I can evaluate it?

    A computer restart was costing the day the day to solve the problem.

    Installation of the toolkit does not have a reboot of the system, but it seems to need i.

  • Hide the Excel using LabVIEW Report Generation Toolkit or active chart legend

    Hello Eveyone:

    I'm working on tool report generation in labview and creat excle report. I create the chart in the report, but I can't hide the chart legend or change the font size using the report generation tools.

    I appriciate you guys time.

    Thank you

    Howdy!

    What version of LabVIEW Report Generation Toolkit you use? Did you take a peek at the .vi LabVIEW example column chart (Excel)

    and he looked at using the Excel insert graphical VI and Excel graphic Set do?

  • Error 7 with Report Generation Toolkit

    Hi all

    I am trying to generate an Excel sheet report for some readings using the "Generation of reports toolkit", but when you try to generate the report, the code generation report part is executed and gives Error (7) and there is no report is generated.

    The Code I use is attached in the following link:

    https://www.dropbox.com/s/9n4brimucsd0xts/report%20Generation.rar

    Can I get help please?

    Thanks in advance

    I could download and open your compressed file.  I unpacked it in a folder.

    There are many features that lead me to ask "you try to learn LabVIEW on your own, without a mentor and training and orientation?  Here are some of the things that I noticed:

    • Although a generation of .lvproj, .aliases and .lvlps project, open file reports, was empty!  Because projects have been added for LabVIEW, almost all development should be done in a project, but you don't seem to do.
    • You have an event loop (good) to manage the keys Start, Stop and report.  But instead of using Boolean control with a property and using an event "Changed value" latch, you use switch to published (which, so far, I've never used) and a mouse down event.  I guess this could work, but I've never seen this model.
    • You write an Excel report, but do not use the Excel-specific screws (for example Excel easy table).  Why or why not?  The basic idea of an Excel report, is that you create 2D text data, you want to write in Excel, then with a few simple screws, you open Excel, write the Table, and then save the report.  In particular, you do not write something that resembles the columns and rows on a worksheet (Date, time, Test, etc.).

    Now to your specific questions, error 7.  Do you know what means this error?  If you click Help, choose error explain, and set 7, you will see that it means "file not found".  Well, there is a place prominent where a file is used, just at the start of your program.  I recommend that you put a probe (do you know probes?) or an indicator on the way past in the hand for a loop and see what file you are trying to open (hint - there is an error in the way you build the path, but you should be able to understand how to fix it).

    Good luck.  Hope these suggestions you get on a better path.

Maybe you are looking for