-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

Similar Messages

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

Hi Leo22,
Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

Problem with writing continuous data to excel using using Report Generation vi's

Hey Everyone,
I am trying to read the data from DAQ and write to excel continuously using Report Generation vi's.
But when I run the VI, it writes only one interation of the while loop (gathering data from DAQ continuously) and doesn't append the data into the same file when I run it again after stoping the VI.
I have attached the VI i created. Please let me know if you have any idea to solve this issue.
Thanks
Attachments:
sample 5.vi ‏35 KB

There are two problems with your VI. First, the basic logic of writing/appending to a file (Excel, TDMS, anything) should go something like this: Open the file, position yourself at the end of the file, then, in the loop, acquire data and write it to the file until you are finished with data acquisition. When you exit the acquire/write to file loop, then close the file. In particular, the opening and the closing of the file should not be inside the loop.
As others have pointed out, writing to Excel might not be optimal, particularly if you are acquiring data at a high rate (and would therefore be writing a lot of data). We actually use Excel in our data acquisition routine, mainly reading from a WorkSheet to get the parameters of a particular stimulus, but also writing the outcome of the response to the stimulus. As it happens, our "acquisition rate" in this example is on the order of several samples per minute, so there's no problem using Excel (we also sample 16 channels of analog data at 1 KHz -- this gets written as a binary file).
Second, if you really do want to use Excel, use the (existing) Excel file to which you want to append as the "template" argument of the New Report function. Then use the Excel Get Last Row function to position yourself at "end of file", as noted above.
Good Luck.
Bob Schor

Error when using Report Generation Toolkit

Hi, all,
I am using Report generation toolkit to generate a report in either
word or excel format. But i even can't run the "new report.vi". It
returns an error code of "Bad variable type (-2147352568)", and seems
this error comes out from the "call by reference" after the
word/excel's "open VI reference". I have checked the folder
"C:\Program Files\National Instruments\LabVIEW
6.1\vi.lib\addons\_office", there are "_exclsub.llb" and
"_wordsub.llb". The respect VIs are all inside. I don't know why there
is such error. Currently i am using labview 6.1, Microsoft office 2000
and Windows NT 4.0.
Your kindly help will be appreciated very much!!!
Thannk you in advance!! ^_^
Your sincerely,
celery

So, if you place just New Report.vi on the Block Diagram, wire in the report type and run it, it gives you this error? Do the example programs which ship with the toolset give this same error also? If so, I would just reinstall the toolset first and see if that helps. It sounds like the entire install is corrupt.
J.R. Allen

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

How to populate the last empty row in Excel without using Report Generation Kit

I wrote a Labview SUb Vi that uses Report Generation Toolkit that is not loaded on the test stand. I am looking to convert it from Report Generation Vi like New Report, Append Table to Report, Dispose Report. The tunneling through all the report generation Vis seems extensive. Code is attached. Thanks, Greg
Greg

Thank you that was a big help...
I used the Excel Forum to get a lot of great ideas. My code is almost working.
There is a 2-D String Array that represents the String data that I am exporting to the Excel File Sheet 1 - 5.
I am attempting to determine the last populated row in sheet 1 then populate the next row of Sheet 1. Since all 5 sheets are populated every time, I should not have to search every sheet for the last row.
I am getting two row populated on sheet 1 with seeming the same data.
I found an AXExcelWrite2D ArrayWorksheet.vi that I thought would work. I think there is a Table determination that is causing me problems. The link is http://lavag.org/topic/13324-labview-and-excel-activex-or-ado/. The Application Invoke Node has a convert formula with "FromReferenceStyle" with R1C1 Attached to it. I am not sure what this function is doing. When I try to bring the function help up, there is a missing file.
I am including both the new active x vi and the report generation vi. Report Generation VI works.
I would appreciate any assistance I can get on this.
Thanks
Greg
Greg
Attachments:
REPU Test Data Population using Active X Write Save.vi ‏92 KB
REPU Test Data Population.vi ‏60 KB

How to import pictures into excel sheet without using report generation

Dear Friends
I want to know how to import the picture or picture file into excel sheet without using report generation..
kindly come up with any suggestions or example code
Regards
Karthick
Solved!
Go to Solution.

Thank you Rajesh
i am going through that vi
Rajesh Nair wrote:
Please go through below link
http://zone.ni.com/devzone/cda/epd/p/id/3638
Eventhough one subVI is missing i think it will be usefull for you.
Regards
Rajesh R.Nair
Rajesh Nair wrote:
Please go through below link

Labview using Report generation toolkit in 2011 run time engine

is that possiblity to run the word in labview using Report generation toolkit in 2011 run time engine

It is possible to use the Report generaion toolkit with the run time engine. But you will have to include a lot of VIs from User lib since the report generation toolkit uses a lot of dynamically called VIs and classses.
Certified LabVIEW Architect
Certified Professional Instructor

Error 1045 Using Report Generation Excel 2010

Hello,
The attached code throws an error 1045 when using Excel 2010. I don't get this error when using Excel 2007.
Please Advise
Thanks
Attachments:
Source.zip ‏66 KB

Take a look at this Knowledge Base article and see if if helps.
Error 1045 When Using Report Generation Toolkit for Microsoft Office
http://digital.ni.com/public.nsf/allkb/3E4102D8B91D0F9E86256CE0006BADCB
Applications Engineer
National Instruments

How to justify the values in table using report generation tool kit

Hi
How can we align the values in excel table using report generation toolkit.
like left,right,center.
Regards,
hari
Attachments:
Report_excel.vi ‏34 KB
New Bitmap Image.JPG ‏134 KB

Hi,
A trigger is designed to be a part of a transaction, not it's end.
It is like following these steps (not really accurate, but should give an idea):
1. programA issues INSERT statement on tableA
2. 'control' goes over to the database
3. constraint checks happen
4. the associated triggers on tableA do their work (e.g. fetching a sequence value for a primary key)
5. 'control' goes back to programA
6. programA decides if a commit (no error occurred) or a rollback (error case) has to be issued.
Did this help? Probably not, I'm not happy with what I wrote, but anyway... :)

How to write data which i am reading from spectrum in excel using Report Generation toolkit.

Hello All,
I wrote code for reading data from Spectrum analyzer and also for writing in excel using report generation toolkit. When i run program values get read and excel sheet opens also but i cant see anything written in it.
So if anyone can help me in this i will be very gald. I am attaching screenshot of my program and also attaching .vi file. As i am using drivers you can see some of vi.
Thanking You,
Pallavi
Solved!
Go to Solution.
Attachments:
Channel_Power.jpg ‏123 KB
Channel Power_Toolkit.vi ‏64 KB

Hi Palavi,
you try to select a specific worksheet what is not existing, therefore just select "Channel Power" (and not Power Channel) and it should work for you.
Regards,
Tobias

Unmerge cells using report generation

Hi,
I have an issue using report generation toolkit, I'm writting text data to a range of cells and the cells get merged because of that. So I need to unmerge cells in order to be able to write again in thoose cells, because if the cells are merged writing cause an error.
I have found a VI in the report generation toolkit to merge cells but I can't find one to unmerge them.
Is there a way to do that?
Thanks
Olivier

Hello Olivier,
What version of LabVIEW do you have?
How are the cells getting merged?
Can you provide information about the error message you are receiving?
Regards,
Juan Galindo
Applications Engineering
Juan Galindo
Applications Engineer
National Instruments

Problem building application using Report Generation Toolkit, LV 2011

I'm using LabVIEW 2011 under Windows 7.
I tried to use Application Builder to create an executable from a large body of code. One thing the application does is load VIs into a subpanel and run them.
Application Builder created the executable and gave no error message. The built application ran except that it couldn't run any of the dynamic VIs.
I finally succeeded in doing a screen grab on a transient dialog (about 1/10 sec. appearance). The dialog showed an attempt to load <vilib>:\Utility\NIReport.llb\NI_report.lvclass.
In one dynamic VI I commented out the call to the only VI that uses the Report Generation Toolkit (called only from dynamic VIs, all of which call it). Sure enough, when I built the application with that change and ran it, the dynamic VI that didn't invoke the Report Generation Toolkit did successfully load into the subpanel and run.
So, trying to prove to myself that that was the only problem, I wrote a VI that does nothing but load a VI into a subpanel and run it. User can choose one of two VIs: one that doesn't call the Report Generation Toolkit (or do much of anything), and one that does. Both VIs run fine standalone.
The not-much-of-anything VI loaded and ran in the subpanel. The other VI didn't--the same dialog, mentioned above, popped up for 1/10 second or less. Screen grab is attached.
When I included LVClass and NIReport.llb folders in the project (from vi.lib\Utility: Snapshot folders), and "Always Included" those folders (per a suggestion on this forum from a few years ago), the result was the same. The result was also the same when I included either one of those folders but not the other. Likewise it doesn't matter whether I add the dynamic VIs as "Always Included" or not.
Another piece of information that may be pertinent: when adding the NIReport.llb folder, I got a message that it was impossible to add a certain VI that's part of some report-type class, because a VI of that name already existed in the project. Screenshot of that dialog is also attached.
VIs and project file are also attached along with the two screenshots. I hardcoded VI paths, so put everything into C:\Testing if you want to see what the code does--or hack as desired, etc.
I will be deeply grateful for any help! And I apologize in advance if there's already some exact or close-enough solution posted--but I doubt there is. I looked around.
Thanks very much,
mws
Attachments:
Test-App-Build.zip ‏336 KB

Hi again,
If you extract all files in the original zip attachment to a folder called C:\Testing on a Windows 7 machine running LV 2011, and then use the build script within the project file to build the application, you can run the application and see what happens. You can also play around with the build parameters, rebuild, run, and see what happens then. You can also open my VIs and see what I'm doing.
The application lets you pick one of two dynamic VIs to run in a subpanel. One VI contains calls both to Report Generation VIs and some functions from the Advanced File Functions palette. The other VI does not.
When you pick the first VI to load and run (the one with the Report Generation and Advanced File Functions calls), it loads into the subpanel but is not executable.
When you pick the second VI to load and run, it does load into the subpanel and execute. So there's nothing wrong with the way I load and run a VI in the subpanel.
In the development environment, the whole thing runs with no problems.
Evidently the built application has problems resolving paths of something called by Report Generation VIs and by the Advanced File Functions I use.
I've done a lot of experimenting and no luck. I've looked in forum archives, etc. etc., for possible solutions. I'm hoping there's some simple solution I've missed.
Thanks very much for any help!

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

.tdms report generation with .pdf format

Hi,
My problem is a kind of report generation problem.My data logging format is .tdms format and i use tdm file viewer function to view my datas but i didnt use tdm data report generation function.How can i use this function with my code.Actually i want to print automatically like pdf format...
Attachments:
ustalt.vi ‏62 KB

kacco wrote:
Hi Yye,
İ use diadem and labview 09. I know diadem is very good solution to view data but i want to print automaically.My data type is .tdms(test data management system) if u look my .vi you can understand.
ı want to print aoutomatically with my channel and group.
I can see from your code that you are a beginner. Your coding style is very Labview no-no. But well every Labview pro have some time been a beginner I have some problems understanding or grasp the essence of your problem. Can you post your failed attempt to use rapport generation. It would help in the understanding of your problem.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

-1073741819 code using Report Generation with LV 6.1

Similar Messages

Maybe you are looking for