LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

question about empty template in MS word toolkit generation


@ben64 wrote:

@Bob_Schor wrote:

I should have noted that I ran my test on a Windows 10 x64 system, Office 2013 (64-bit), LabVIEW 2016 (32-bit).  I'll be "out" tomorrow, but if there's no resolution, I'll try on Wednesday to test on a Windows 7 x64, Office 2010, LabVIEW 2012/2014/2016 system.  I think I also have a LabVIEW 2011 VM (but I may have discarded it ...).

 

Bob Schor 


I tried LV2012, 2014 and 2015 with Office 2010 and the result is as expected (only 2 columns). Using Windows 7 pro

 

Ben64


I am using LV 2011 on word 2013, do you think it is a version issue?

Now on LabVIEW 10.0 on Win7
0 Kudos
Message 11 of 19
(1,089 Views)

@aputman wrote:

Turns out, after doing a small amount of research, it is possible to add a chart to a Word document (using the code below) but the method for editing the dataset (in an Excel worksheet) is not available.  Are you required to use Word?  If not, I suggest to use Excel and the method above.  If Word is required, you can use the Excel method above, save a picture of the chart and load that into your Word document.  

 

Example_VI_BD.png


Can you please post in LV 2011 version? I can't find the InlineShapes property node.


Secondly, yes, I am limited to use WORD as I have to add other items to my report as well, graphs are just 1 part of the report

Now on LabVIEW 10.0 on Win7
0 Kudos
Message 12 of 19
(1,086 Views)

That VI is on the RGT pallete -> Word Specific -> Advanced -> Word Get ActiveX References.

 

This is not version specific.  I have LV2011 installed and I get the expected output with Word 2010.  

aputman
------------------
Heads up! NI has moved LabVIEW to a mandatory SaaS subscription policy, along with a big price increase. Make your voice heard.
0 Kudos
Message 13 of 19
(1,076 Views)

you have Word 2010, I have word 2013

Now on LabVIEW 10.0 on Win7
0 Kudos
Message 14 of 19
(1,069 Views)

@LV_Enthu wrote:

@ben64 wrote:

@Bob_Schor wrote:

I should have noted that I ran my test on a Windows 10 x64 system, Office 2013 (64-bit), LabVIEW 2016 (32-bit).  I'll be "out" tomorrow, but if there's no resolution, I'll try on Wednesday to test on a Windows 7 x64, Office 2010, LabVIEW 2012/2014/2016 system.  I think I also have a LabVIEW 2011 VM (but I may have discarded it ...).

 

Bob Schor 


I tried LV2012, 2014 and 2015 with Office 2010 and the result is as expected (only 2 columns). Using Windows 7 pro

 

Ben64


I am using LV 2011 on word 2013, do you think it is a version issue?


Those versions are not compatibile. See link below

 

http://digital.ni.com/public.nsf/allkb/C9408B9F08D711E786256F3300701D01

 

 



-Matt
0 Kudos
Message 15 of 19
(1,058 Views)
Could be because according this Report Generation Toolkit Compatibility with Microsoft Office and LabVIEW http://digital.ni.com/public.nsf/allkb/C9408B9F08D711E786256F3300701D01
--LabVIEW (Report Generation Toolkit) 2010 supports Microsoft Office XP, 2003, 2007, 2010 and Not "2013"
Thanks
uday
0 Kudos
Message 16 of 19
(1,055 Views)

oh no!! that's a bummer... what could i do now?

Now on LabVIEW 10.0 on Win7
0 Kudos
Message 17 of 19
(1,052 Views)
Either downgrade MS Office or Upgrade LabVIEW to 2014 which supports Office 2013.
Thanks
uday
0 Kudos
Message 18 of 19
(1,049 Views)

@udka wrote:
Either downgrade MS Office or Upgrade LabVIEW to 2014 which supports Office 2013.

Unfortunately, I can't do either of them, as almost all my work is done in LabVIEW 2011, and the company won't fund it. 

Similarly, the policy is to use Office 2013 

Now on LabVIEW 10.0 on Win7
0 Kudos
Message 19 of 19
(1,047 Views)