Report generation toolkit problem with office 2000 and office XP

Hello, I am having a problem with running my vi after it is compiled with application builder. The dev machine is an XP box and the targer is windows 2000. I included _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi from the office 2000 section of the install cd (for the report toolkit) in the compile but did not include those files for XP. When I run the application on the target machine (2000), the reporting functions call Excel just fine and the program does not come up with any errors. The program however, is not loading the approprate template and inserting the approprate data. Did I leave some neccessary files out of the compile? Thanks in advance!
Greg
Gregory Osenbach, CLA
Fluke

Hi Acer,
The recommended procedure in your case is to install Microsoft Office 2000 on the development machine and then reinstall the LabVIEW Report Generation Toolkit. When the toolkit is installed, it will check for the current version of Office and install the corresponding VIs to support it. The VIs include different ActiveX calls according to the version of Office. Therefore it is not enough to change the support manually without having the correct version of Office installed first.
However, I would recommend that you just try to run your executable on a machine that has Office 2000 installed. The difference in the ActiveX API for Office XP and 2000 is not that significant, so your application might work perfectly on an Office 2000 machine. If you try to run the executable on a machine with Office 97 installed I'm willing to bet my right arm that you will experience errors.
Good luck Acer!
- Philip Courtois, Thinkbot Solutions

Similar Messages

Report Generation Toolkit failure with Win 7 and Labview 2013

I recently had my computer updated to Windows 7 and am now seeing a problem with the Report Generation toolkit (version 2013) when working with Excel files. If I try to run the New Report.vi with report type Excel selected I get error -2146777998. Doing the same thing with Word selected eventually opens Word, although this takes about ten seconds, but it does not generate an error. Selecting Standard Report or HTML also run without errors.
I've researched this error on line but I keep ending up .NET and C# forums where everything goes over my head. Has anybody got any suggestions?
Solved!
Go to Solution.

I found the solution to this particular source of error code -2146777998. There are two template files that reside in C:\Program Files (x86)\National Instruments\LabVIEW 2013\templates\Report by the name of MSOffice_RGT_Template.dot and MSOffice_RGT_Template.xlt. The problem came down to that these templates got corrupted somehow during the fresh install. As soon as I replaced them with versions from another machine the problem disappeared.
Just as a side note, I discovered the problem by kicking off the MS Office Report Express vi and out came a much clearer message that aimed me at the templates. Not quite sure why that message isn't echoed into the individual subvi's on the pallette, but life is a mystery.

Report Generation Toolkit Compatibility with Microsoft Office 2013 and LabVIEW 2012

Hello community,
on this page there is shown the Report Generation Toolkit Compatibility with Microsoft Office and LabVIEW.
In our company we use actually LabView 2012 and it works perfectly with MS Office 2010.
Has anyone ever tried the "Report Generation Toolkit" of LabVIEW 2012 with MS Office 2013? Does it really not work? Has anyone an emirical value for this topic?

Hi digital_badger,
as you sure have seen in the link it is not officially supported by NI, which means to you one of the following things:
1. You could upgrade your LabVIEW and your Report Gerneration Toolkit to Version 2014 and use MS Office 2013
2. You could just try it with MS Office 2013 which might work but if it's not working you don't get any support from NI.
Even if someone tried it already and it worked for him does not mean that it will work on your machines. It is possible that on some of your machines it could work but not on others. Their can be a lot of problems while playing around with unsupported setups.
3. You could leave your setup as it is and stick to your MS Office 2010.
I hope I could give you a good answer to your question

Report generation toolkit problem

hello everyone,
i am using Export waveform to Spreadsheet.vi for getting data into excel. i have downloaded and install the Report Generation toolkit 1.13 for make it working but still it seems not working
i am using labview8.6 on windows xp with Microsoft Excel 2003 .
i have tried the same vi on an other computer with same configuration and it works there, but not on my PC, i want to ask is there any thing wrong with my version and the Report Generation toolkit? or i am installing it wrong? or is there any specific folder or path i have to mention during installation of toolkit? if yes then how could i uninstall the existing toolkit because i couldnt find the installed toolkit path or location on my PC?
thanks
looking forward ...

Hi Hussain,
Are you still having these problems.
Can you use other functions in the toolkit or is it just that one.
Do you have other versions of labview than 8.6 intalled on your computer ?
/Christine

Word report generation toolkit error with Win 7 LabVIEW 2013, Word2010

Hi All
I'm seeing different Errors using the Report generation toolkit. Maybe you can help me with that.
The errors are:
-2147417846, application is busy in Word_Get_range.vi
-2146824090 Exception in Microsoft word: Befehl misslungenHelp Path is wdmain11.chm and context ...
-2147417846 application is busy in Word_Quit.
the error messages are attached to the post.
I'm testing 10 sensors with one application and want to run up to 5 applications on one computer. Since I'm seeing such errors as application is to busy I set all my report generation vi's as non-reentrant execution and additionally added some pause after each word modification.
But I'm still seeing such errors when I run two applications on one computer.
What is the best way to deal with these errors?
thanks
best regards
Urs
Attachments:
exceptionerror.PNG ‏20 KB
BusyActiveX2.PNG ‏20 KB
BusyActiveX.PNG ‏22 KB

Here my Vi's involved in creating the report.
Is there a way to check wheter word is busy or already open?
Attachments:
save report as PDF.vi ‏26 KB
create_report.vi ‏70 KB
Word_Update_Table.vi ‏34 KB

Having problems with OPA 10 and office 2007 templates

Hi,
I have a OPA 10 and office 2007 set up which is having some issues with the macros. Seems to me that the visual basic code is not kicking off really well sometimes. I am trying to map the sequence which leads to the errors and I believe that the issue is around opening an old word doc which has a old template version (.dot). This may be the cause for OPA getting lost when working with word 2007.
For example, I ask to open a rules doc and the visual basic tells me that OPA couldn't open the doc but word is opening the doc anyway. However none of the toolbar commands work as well as I can 't save the doc etc.
Have you experienced any issue with OPA 10 and Office 2007? Any special word configuration? Should i go back to office 2003?
BTW, I have both dotm and dot templates loaded as add-ins in word. The dotm toolbar looks good but the dot toolbar is a bit strange in 2007.
Cheers,
Paulo

Hi Paulo,
Have a look at the following tips from Davin Fifield about troubleshooting the toolbar.
Sometimes when using Oracle Policy Modeling, Microsoft Word documents that are part of a Policy Modeling project may appear without the OPA toolbar (in Office 2003) or OPA options on the Add-Ins ribbon (in Office 2007) when opened in Microsoft Word.
This problem can be caused by various factors.
Here are the top three troubleshooting steps to try to recover from this situation.
1. With your project open in Oracle Policy Modeling, run Update Oracle Policy Templates from the Tools menu. This will attempt to make sure the correct Word template is attached to each project Word document that is not currently excluded from the build. Open a Word document to see if the toolbar/ribbon is now displayed correctly. If not, continue to step 2.
2. Try changing the UI language for your project. To do this, choose Options, from the Tools menu in Oracle Policy Modeling. Select Environment. Selet General. Under Authoring UI Language, choose a language other than your preferred UI language, and click OK. Then repeat these steps to revert to your preferred language. Open a Word document to see if the toolbar/ribbon is now displayed correctly. If not, continue to step 3.
3. Open one of the Word documents in your Policy Modeling project. Run the macro UpdateToolbar: In Word 2007, choose the View ribbon, then select Macros/View Macros, highlight the UpdateToolbar macro, then choose Run.
Does this resolve your issue?
Jasmine

Excel activex call changes between Office 2000 and Office XP. How does one manage that?

I have several Active X calls from within a VI. One in particular is
the Excel Cell Value property node in Office 2000. MS has decided to
call it Excel Cell Value2 in Office XP.
I have built and exe on a machine with Office 2000 and can run the code
on a machine with Office XP, but I can not build on the machine with
Office XP. I can also run a VI with that call
on the Office XP box, but if I mass compile the VI I get the broken arrow.
I guess I am confuesed as to why it can run but not compile. If the
ActiveX call is not there for the compile why is it there for the run?
If I can expect this does it work in reverse where I
build on an Office XP box and run on a Office 2000 box?

These problems you are experiencing do stem from the ActiveX changes between Excel versions. When you mass compile LabVIEW checks to see if everything is linked correctly, including ActiveX portions of your code. Since there are slight changes the LabVIEW compiler detects something is wrong, but cannot isolate the problem. You might need to force a recompile of that VI. Check out this link.
http://digital.ni.com/public.nsf/websearch/50D06DEE8B9DC018862565A0006742F2?OpenDocument
Hope this helps!
Andy F.
National Instruments

Communication problem with FP-2000 and Labview 7.1

I am using the FP-2000, DO-403 and TC-120 modules with Labview 7.1, being run on a host computer via an ethernet connection. The setup has operated flawlessly for ~2 years; recently, I have noticed that while a VI is running on my PC, connection to the FP module ceases. There is no pop-up "connection error" in my VI, and the all the power and status LEDs on the FP modules are normal. I can still interact with the VI on the front panel while it is running, but nothing is passed to the FP module. I have tried communicating with MAX when this occurs and receive a "no connection" message. Is there a simple solution here, such as rebooting the FP module? Or is it time to invest in new hardware?
Justin

I am having a very similar problem with my cFP-1804 and Labview 7.0. I have no problem initiating communication over ethernet, and the vi will run perfectly for hours or even days. Inevitably, however, at some point there is no longer communication with the cFP-1804. Data is no longer being passed either to or from the cFP-1804, and MAX will show that the device is not connected. I also will not see any pop-up error message that says the connection has been lost, either from Windows or from Labview. The vi will just continue to run as if nothing has happened. Turning the power to the cFP-1804 off and then on will always resolve this problem. Since I am using the cFP-1804 primarily for data logging, however, this behavior is particularly problematic as the system will record nothing but zeroes until I discover that the communication has been severed and perform the manual power cycling.
I have been unable thus far to determine the cause of this problem. Any help would be greatly appreciated.
Thanks,
Derrick

Report generation toolkit problem (WORD)

Hello,
i'm trying to display a spectrum with Word (2000). The spectrum is updated
when datas are updated.
It works when i use Vi but if i make an exe file, nothing happens (word
doesn't open)
What's the matter ?
Thanks in advance

Try this workaround until you figure out the problem:
Instead of building your application into an executable, create a simple "loader" application. This is just a VI (with optional professional looking splash screen) that uses VI server to call and run your main VI. If you build this instead, your VIs remain as VIs, and any problems seen such as this are bypassed (hopefully).
I had to use this method when a bug was discovered in VISA (that I don't ever recall being solved, now that I think about it.) that caused it to not work properly in built applications.
I am probably going to author an Application Note or Article in Developer Insights, or LTR about this little trick, as I seem to be suggesting it a lot.
I'm sorry I can't help you with your p
roblem directly, but I hope this workaround helps.
Oh, a side benefit is that you are able to maintain a directory structure. And if you 'release' your software, and have to maintain an archive of the source and released, this makes it much easier, as your executable as only a single file, and all of your source remains intact. It also makes it easier to change your application without having to rebuild. The only drawback is that you have an entire VI Hierarchy as a deployed directory structure. This can be confusing to some people. To me, it was an elegant and optimized solution to many problems. It is a method that I always use now.

Database connectivity toolkit problem with WINDOWS VISTA and Microsoft jet 4.0 provider

Hi again,
I'm experiencing a problem with Database connectivity toolkit and Microsoft Jet 4.0 provider (MS ACCESS mdb database).
I was able to get my application to work properly on my PC: WINDOWS XP PROFESSIONAL, VERSION 2002, SERVICE PACK 3 and Msjet40.dll ver. 4.0.9511.0 (Windows XP SP3 and Security Bullettin MS08-028).
The same connectivity toolkit seems to have problems (although I didn't get any error dialog) on a laptop with WINDOWS VISTA ULTIMATE, SERVICE PACK 2 and Msjet40.dll ver. 4.0.9755.0.
Does anyone have an idea whether it is a sort of compatibility issue or a different thing?
Would it be possible to include my DLLs into the installer in such a way LabVIEW application calls those DLLs instead of the ones it finds on the host PC?
Thanks a lot. Any suggestion or advice very welcome and appreciated.

I ran into this with Windows7 64 but, could not get the jet 4.0 to work. Endnd up dumping access and used sql server express, its free, and all my code worked fine, just used a different UDL to connect. I wasted lots of time trying to find a way of getting the jet4.0 to work with 64bit windows.
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Problems with Windows 7 and Office jet L7500

I have an HP Office jet pro L7555 and since switching to windows 7 I have started to have a lot of problem. I have downloaded and installed the new driver. The problems seem to be sporadic, and are occasionally solved by restarting. I don't want to have to restart all the time! The current error message that comes up is error #30 when I am printing from word. Any ideas?

Have you tried transferring all of your purchases?
To do this, plug in your iPod with iTunes open. (if it starts to sync, let it). Once it's done syncing, keep your iPod plugged in. Go to "File" at the top of iTunes and find "Transfer Purchases from iPod". Click that. It should start transferring everything from your iPod into iTunes. Once it's done transferring, sync your iPod again (just to be safe). Once it's done syncing, unplus your iPod and check each tab on the navigation bar to see if your stuff has transferred and synced (For example, if you transferred music, click the "Music" tab on the left navigation bar, for apps, click "Apps", etc.)
This worked for me when I couldn't figure out why my stuff wasn't transferring from my iPhone to iTunes by just syncing. I have to transfer purchases every time I download a new app, song, book, etc. Hope this helps!

Problem with .docx files and Office 2004

After the upgrade to Snow Leopard, I now am receiving a message "There is not enough memory or disk space to convert." when I try to open a Office 2007/2008 docx file. The error does not happen on all docx files, but only on files over 100kb. The same files that do not work now, all worked prior to upgrading to Snow Leopard. I am using a fully patched Office 2004 (11.5) in addition to the open XML compatibility software 1.1.1 from Microsoft. I have removed all error and duplicate fonts and repaired disk permissions.
I have looked on both Apple and Microsoft for an answer, but nothing except Microsoft claiming Office 2008 will work seamlessly with Snow Leopard.

I just came across this problem too. Very frustrating. I just got this new MacBook Pro last week (so I'm using Snow Leopard too). I installed Office 2004, updated it to 11.5, and installed the open XML conversion software, but no dice. I absolutely should have plenty of memory and disk space to do any docx conversion.
Also, I'm only trying to convert a 20KB docx file, so large file size isn't an issue here. And my copy of Office 2004 is totally legit, in case that's a question.
I really need to be able to open docx files for work, so this is a real problem for me. Help me, Apple-wan Kenobi!
Message was edited by: juliamontgomery

MS-6167 problem with Win 2000 and Winxp

Guys, I am having a problem. After I have installed Win2000 or Winxp Pro( first time boot, it pop blue screen with the msg systemroot\system\ntxxx.dll..I have to turn off and and turn on computer, it let me to boot up.) After that, when I restart the computer it boot up with blue screen(Sometimes, it let me boot up without any problem). I didn't install any third party software(OS only). It's weird. Even though, I have installed FAT file system and the result is the same. I have tested windows 98. It's very stable and no problem at all.Here is my PC configuration
AMD 950
MS-6167
Creative TNT2 Ultra 32MB(AGP)
Sound Blaster Live
Sony DVD ROM
External Modem.
Other than that, I build another PC for my fren here is the configuration
AMD 1.7 XP
MSI KT3 ULTRA
Winxp Pro
Any clue? Do I need to update bios? But I can't find MS-6167 model bios. How come it's doesn't support win2000 and win xp? I got another PC AMD 1.1 Thunderbird with ASUS A7V. I don't have any problem that I mentioned above when I installed 98,win2000 and winxp pro(Separately not dual boot). Appreciate !!!!
Guanyu

heres what i found for another guylink

Problem with QuickLook/Finder and Office 2008 Files...

Hello,
I don't understand what's going on with QuickLook and Finder. I used Keynote and the created files were readable with Quicklook and previewable in the Finder.
Lately, I installed MacOffice 2008. I opened the keynote files with Powerpoint, save it in the same format....and the files are now unpreviewable in Finder and unreadable with Quicklook....I tried to save it in pptx format but I've the same problem....Is it possible to make this files readable and previewable ?
Thanks,
RedVivi

Solved with 10.5.2 update

Report Generation Toolkit on Vista and Office 2007

Hi,
I am trying to install Report Generation Toolkit 1.1.2 on LabVIEW 8.5 on a computer with Vista Business and Microsoft Office 2007.
The installation is starting, but I am receiving a message saying that "Microsoft Office 2000 or later is not detected on the computer"
The installation stops and the toolkit is not installed.
What can I do ?
Tom

Tom SAVU wrote:
Hi,
I am trying to install Report Generation Toolkit 1.1.2 on LabVIEW 8.5 on a computer with Vista Business and Microsoft Office 2007.
The installation is starting, but I am receiving a message saying that "Microsoft Office 2000 or later is not detected on the computer"
The installation stops and the toolkit is not installed.
What can I do ?
Tom
The Report Generation Toolkit does probably not support Office 2007 yet. This is because the Office ActiveX interface used to change with each version and the Report Generation Toolkit comes with specific libraries for each of the Office versions it supports. With the wrong office version the Report Generation Toolkit VIs are normally broken and can't run without some more or less involved modifications.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Report generation toolkit problem with office 2000 and office XP

Similar Messages

Maybe you are looking for