Report generation set font vi messed up

Hello all,
I am not sure if I am the only one who has had this problem.  I
just upgraded to the developer suite professional editon.  I
installed the software and then installed the Report Generation
Toolkit.  None of my VI's I had written that used the Report
Generation Toolkit would execute.  It affected these VI's, at
least these are the two I have found, Excel Easy Text and Excel Easy
Title.  The Set Report Font.vi  had all the input terminals
connected to the wrong type.  I was able to reconnect the inputs
to the correct type, but it just has me a little confused.  Has
anyone else seen this or do I have a botched version of Report
Generation Toolkit?
Thanks,
Ben Babb

Hello,
I have not heard of this, but if you encounter further problems please repost.  Also, it will be interesting to see if anyone else has seen this problem!
Thank you,
Best Regards,
JLS
Best,
JLS
Sixclear

Similar Messages

  • Setting the title font and axis labels in a graph created with the Report Generation Toolkit

    I'm using the LabVIEW Report Generation Toolkit for Microsoft Office to generate Excel worksheets containing plots. Unfortunately, the default font size used in the plots is huge (see attached worksheet). I was able to use Excel Set Graph Font.vi to reduce the size of the axis labels, but there does not appear to be a function to do this to the title and legend. In addition, there does not appear to be a function to set the axis text labels. Before I write my own, has NI released additional functions to perform these tasks?
    Thanks for your help,
    Zach Lerner
    Software Engineer
    OnWafer Technologies, Inc.
    Attachments:
    Test1_-_embedded_graph's_title_and_legend_font_is_huge.xls ‏14 KB

    Hello Zeidan
    The graph title and legend font sizes can be changed by accessing a low level VI (Excel_Insert_Chart.vi) that is part of the excelsub.llb that is located at (C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\addons\_office). This VI is called dynamically from within the Excel Insert Graph.vi and it uses VI server technology to access the Excel exposed properties. Attached to this post is an image of the block diagram of this VI after I have modified it to set the font sizes of the title and legend to 15. The circles in the image represent what I had to add to accomplish this.
    Best Regards,
    Ayman Kabire
    Attachments:
    Excel_Insert_Chart.JPG ‏99 KB

  • 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

  • How to set tabstops in MS Word using the LabVIEW Report Generation Toolkit

    Using the Report Generation Toolkit of LabVIEW, I need to set multiple tabstops that very in distance in MS Word.  I also have different sets of tabstops that I use and re-use at different times in the same report.  Is there a way to set the tabstops under program control?  I searched through the various VIs and found that there is a property ("Tabstops", "Word.Tabstops") in the _ParagraphFormat property node that refers to tabstops.  I found it in the Word Format Paragraph (adv) VI.  Unfortunately, I could not determine how to use it.  Any suggestions?  Is this an operational element?

    Bluebell,
    Sounds like you've already done some fantastic work to expose the various properties and methods of MS Word. It took me about 20 min before I could find the specific property that you were talking about! I found it under Word.Document>>Paragraphs>>Tabstops>>Add. There is a position, alignment and leader parameter that you can set from this property node. I've found that the best way to discover what these parameters do is to simply experiment. You could also try using the macro recorder in Word, perform the specific task, and then look at the code generated. I'm guessing that position sets the position of the tabstop itself. It sounds like your application is really specific. For such a specific task, I think I'd write a macro and call that macro from LabVIEW.
    Chris Cilino
    National Instruments
    LabVIEW Product Marketing Manager
    Certified LabVIEW Architect

  • Setting Fonts in Custom Reports

    Hi,
    How do I register my reports (written in reports 2.5) in inventory 11 without my fonts losing its format?
    You see my reports when run separately display my fonts correctly but not when I register it.
    Thanks for any help you could give.

    Oracle Applications reports Drives the Fonts ,size attributes from the Printer driver assigned to it.Since most of the Styles are Character mode you will get only Courier 10 Fonts.
    If you need other fonts you may need to register your report as POSTSCRIPT .You may require R60RUNB to run the Post script reports.

  • Report-generation vi problem

    On a Windows XP system using the "Text Report Example" vi, the (read) report property node item "TextFont" (stdole.Font) at the beginning of the "Font Style" vi which is a part of the "Set Report Font" vi is returning this error:
    "-1073741819 Unknown System Error in Font Style.vi->Set Report Font.vi->Easy Text Report.vi"
    Any suggestions as to a cause and cure?

    This Knowledge Base from NI's website actually deals with this problem. The fix depends upon whether or not you have the Report Generation Toolkit for LabVIEW. There are fixes for whether or not you have the Toolkit. Hope this helps.
    J.R. Allen

  • -1073741819 code using Report Generation with LV 6.1

    I'm studing about the Report Generation Functions with LV 6.1, and I'm trying to run some example about it, but the programs sends the next error: "Error -1073741819 ocurred at unknown System error in Font Style.vi> Set report font.vi>Easy text report.vi
    >. I'm using Windows XP plataform.
    someone knows what can I do?
    Thanks for your help

    Maybe you already know this but the font settings is a cluster of 4 elements: 2 integers and 2 strings. The 2 integers are character set and weight. They default to -1. The two strings are font name and font size. The default to blank strings. Are you wiring this cluster into your font settings terminal? Do you have -1, -1, Arial, and a number for font size inside the cluster (I use 4 for HTML reports)?
    - tbob
    Inventor of the WORM Global

  • Report generation: server execution failed

    the app has been running for months. IS dept just upgraded machines and software. NT4.0 is now Win2000 and Office 97 is now Office2000. Report generation tool kit is not happy. Even running NI examples I get error -2146959355 server execution failed in Font Style.vi
    Lawrence M. David Jr.
    Certified LabVIEW Architect
    cell: 516.819.9711
    http://www.aleconsultants.com
    [email protected]

    Searching the Microsoft's web site, I found some info on this error:
    If you have never had Norton AntiVirus installed on your computer, follow the following instructions:
    1. Open up the specific VI causing Error �2146959355
    2. Recompile this VI by pressing the Run arrow while holding down the CTRL and SHIFT keys
    3. Go to File � Save All
    4. Run the VI
    If you are using Norton AntiVirus 2000 with Microsoft Word 2000, follow these instructions:
    Note: This information was provided by http://support.microsoft.com. Please use these instructions at your own risk.
    1. Select Start � Run
    2. If Norton AntiVirus is installed as a stand alone application, type:
    regsvr32 -u "c:\program files\norton antivirus\officeav.dll"
    If this is successful, you will receive:
    DllUnregisterServer in C:\Program Files\Norton AntiVirus\OfficeAV.dll succeeded.
    If Norton AntiVirus is installed as a component of SystemWorks, type:
    regsvr32 -u "c:\program files\norton systemworks\norton antivirus\officeav.dll"
    If this is successful, you will receive:
    DllUnregisterServer in C:\Program Files\Norton Systemworks\Norton AntiVirus\OfficeAV.dll succeeded.
    3. Click OK
    Microsoft notes that in some cases you must rename the oleaut32.dll and reinstall Office 2000. Renaming oleaut32.dll usually requires that you boot your computer in MS-DOS mode.
    - Navigate to the directory where oleutt32.dll is located (usually C:\windows\system32) using the cd DOS command.
    - Type: rename oleaut32.dll renamed_oleaut32.dll and press Enter
    - Reinstall Microsoft Office
    Note: This problem seems to still exist with Office 2002.
    1. Unfortunately, this is how the activeX works. If Microsoft changes the activeX objects from one Office version to another, the executable built with Office97 will not work with Office2000. You will have to recompile your VI into the executable on a machine with Office2000 and toolkit configured for this version.
    2. For the error "server execution failed" with Text Report Example, select File � VI Properties. Select "Execution" from the category box and set the "Preferred Execution" to user interface. This should solve the problem.
    Zvezdana S."

  • 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

  • What is wrong with the report generation toolkit????

    OK.  Now I'm a little frustrated.
    I started this thread, but then made an ugly workaround until someone tells me the correct solution.
    So now.... my compiled application can find all the toolkit VIs... but I get error messages telling me that the VIs were are too old (V 7.0) to be recompiled to Version 8.5.1.
    When I got the first of these messages, I opened and saved the VI indicated.  That just pushed the problem along to the next VI.  So I said "ah ha!" and went to the directory (blah\blah\....\addons\_office) that has the toolkit routines and did a Mass Compile.  No errors were generated by this.
    NOW when I try to run, I get an error message telling me that Excel_Insert_Text.vi is not executable.  But that is clearly a lie.  When I open the VI in the development environment, there are no broken arrows...
    And let us not forget my application runs perfectly and without errors in the development environment, even after I brutally recompiled everything.
    For those who care:  I'm running V 8.5.1 with whatever version of the Report Generation Toolkit comes with that (1.1.2??).
    Arrgh.
    -GN

    I feel your pain GN... the RGT in its current Classes incarnation has a few "issues"... try deploying it with TestStand a whole world of pain opens up.
    Now, I have recently seen an issue very similar to the one you described, I broke the RGT after doing a mass compile.
    Eventually opened the RGT VI that was "broken", it looked fine to me. It was something to do with setting the font, and was basically just an activex call. Eventually out of frustration I right clicked on the node, reselected the same method, and another input parameter line appeared at the bottom of the node and the VI all of a sudden became runnable. WOW!
    This needed to be done in a few of the VIs.
    Maybe this will help you
    nrp
    CLA

  • 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

  • Report generation Footers

    Greetings all... hope someone can help.
    I inherited a huge Labview application that works well. I have been tasked with cleaning it up and adding some info to the report. The report uses the Report Generation Vi's including New Report, Append Image to Report, Set Report Font, etc... New Report is set to Word type. Report Generation Toolkit is installed. I am trying to add a footer to the report. I can do that easily enough, however, it seems like the footer is limited to 2" in length. As a result, the last 5 characters of the footer wraps to the next line. It does not matter whether I select left, center, or right. The footer is 25 characters long, and the font size is 12 (standard). The system is running Word 2007. I can't for the life of me figure out how to get the footer to accept a longer text string.
    I have attached an image of the section of code in question. pls... be nice lol  As I said, I inherited this and not much planning was done as to how the report would look at the time. You will see a string constant comprised of a number sequence going into the footer report vi. This is for testing only and allows me to see easily how many characters it will accept.
    can anyone help??????
    Attachments:
    labview image.jpg ‏238 KB

    Hi Franco,
    Much like when you write a document in Word, there is just a set limit to the amount of text you can fit across one line of the page.  Much like you can in Microsoft Word when editing yourself, you can use the Set Report Margins VI to set the margins to be smaller so that more text will fit on the page.  Apart from making the text's font smaller, this is one of the few solutions to fitting more text per line.  Thanks!
    Stephen Meserve
    National Instruments

  • Report Generation Toolkit Table Row Height-MS Word

    I am having trouble setting the table row height in the report generation toolkit. I can set the column width fine, but the row height seems to remain the same no matter what I set it to. I have attached the VI that generates and formats the table, and the printout it is resulting in. I have also attached the template file I am using.
    Any tips to get this to work right? I am trying to make the cells exactly the same height as the text inside. 
    Solved!
    Go to Solution.
    Attachments:
    AddMarkersToReport.vi ‏20 KB
    badFormatting.pdf ‏179 KB
    splitter.docx ‏13 KB

    Hi,
    So I tried .2  and it didn't work.  So I went to Word to manually change it, and it did not work either.  There is a selection box in word, for the table properties, that seems to default to the value "at least".  When I changed this manually to "exactly" in word, no problem with the .2 manually in Word.
    Hopefully this can be set within the template, for all new inserted tables.  I'm not sure the report generator VI's expose this property.  Well, this is a start for the issue.
    Edit ****
    You can go into the add table VI and expose the property.  See pic.   However, you have to decide if you want to "upgrade" this VI permanently to expose this property or make a copy with the property exposed.   I haven't messed with the new class reports too much, so not sure of the ins and outs with this.
    I think this is the issue with the row size becoming smaller.
    Mark Ramsdale

  • Word report generation problem

    I have a problem with my report generation toolkit. I have programmed a test program (main_program), where i can load a data and print it to a word document.
    First i have to load the data(data.txt) and then i have to push the print button.
    The header of my is ok, but when the Subvi (write2) tried to generate the graph in the Document always an error occured!
    I got an error message but i don*t found the reason why the program stops!?
    Error Message:
    Fehler -2146827284 ist bei Exception occured in Microsoft Graph, Die Interior-Eigenschaft des Series-Objektes kann nicht zugeordnet werden.. Help Path is C:\Programme\Microsoft Office\OFFICE11\1031\graph10.chm and context 0 in Word_Set_Chart_Colors.vi->Word Set Graph Colors.vi->write2.vi->Report.vi->Main_program.vi aufgetreten
    Could sombebody help me, please???
    Best regards,
    Peter
    Labview 7.1 on Windows 2000
    Attachments:
    program.zip ‏94 KB

    Another question....
    I want to make a axis label for the y-axis. I can do this with the "word set graph font.vi"!
    But when i make this, the label is horizontally. Where can i change this label to vertical???
    see the attachement....
    Best regards,
    PETER
    Labview 7.1 on Windows 2000
    Attachments:
    word.jpg ‏30 KB

  • Problem with the number format in the graph axis with Report Generation Toolkit.

    Hi!
    I'm trying to use the Report Generation Toolkit to plot some graphs in Excel.
    My first problem is that I don't know how to configure the number format in the Excel Set Graph Font.vi so that my numbers are correctly displayed in the graph's axis. The only given option is general (0,0) but this is not enough for me, my numbers can get really small so I need engineering notation or fraccional format.
    Second: I also insert a table with the graph source data, but the numbers are not correctly displayed either: for example: 
    0,75 is shown as: 
    0,750000
    but 1,25  is shown as: 
    1!250!000
    My guess is I am making to much or wrong string to number conversions or Excel is getting it wrong but I can't find my way...
    Can someone help me with this?
    Thanks,
    Isabel

    Here is my VI, it's just a trial so it can look messy...
    Thanks,
    Isabel
    Message Edited by Isa_pm on 01-22-2007 01:12 PM
    Attachments:
    Create report.vi ‏96 KB

Maybe you are looking for