bugs in "office 2007" or LabVIEW 8.6

[Herbert]

After making a clean install of LV 8.6 I did a "mass compile" on the folder of "addons\_office". However, the operation finished with error messages:

#### Starting Mass Compile: Fr, 30. Jan 2009 19:11:09
  Directory: "C:\Programme\National Instruments\LabVIEW 8.6\vi.lib\addons\_office"
  ### Bad VI:    "Borders and Shading Constant (Table) Shell.vi"    Path="C:\Programme\National Instruments\LabVIEW 8.6\vi.lib\addons\_office\word.llb\Borders and Shading Constant (Table) Shell.vi"
  ### Bad VI:    "Borders and Shading Constant Shell.vi"    Path="C:\Programme\National Instruments\LabVIEW 8.6\vi.lib\addons\_office\word.llb\Borders and Shading Constant Shell.vi"
  ### Bad VI:    "Indent and Spacing Constant Shell.vi"    Path="C:\Programme\National Instruments\LabVIEW 8.6\vi.lib\addons\_office\word.llb\Indent and Spacing Constant Shell.vi"
  ### Bad VI:    "Line and Page Break Constant Shell.vi"    Path="C:\Programme\National Instruments\LabVIEW 8.6\vi.lib\addons\_office\word.llb\Line and Page Break Constant Shell.vi"
#### Finished Mass Compile: Fr, 30. Jan 2009 19:11:25

How come that NI delivers a toolkit that even does not compile without errors? I am amazed and completely disappointed!!!

Herbert

[smercurio_fc]

Which version of the toolkit do you have? Which operating system do you have? Have you checked this document: Report Generation Toolkit Compatibility with Microsoft Office and LabVIEW? Or this document: Which Windows Versions Are Compatible with LabVIEW and the LabVIEW Toolkits?

FOLLOW-UP: Oh, and to your comment: 

---

How come that NI delivers a toolkit that even does not compile without errors? I am amazed and completely disappointed!!!

---

Really. Do you think that NI would still be in business if they did that?

Message Edited by smercurio_fc on 01-30-2009 12:51 PM

[PhillipBrooks]

Why do you need to mass compile the contents of something located within vi.lib ?

[Darren · Accepted solution]

Those are merge VIs for the palettes.  They're supposed to be broken.  Everything's going to be ok.

-D

[Herbert]

I was struggling with the new report generation toolkit as discussed in

http://forums.ni.com/ni/board/message?board.id=170&thread.id=366376&view=by_date_ascending&page=1

and so, before finding that thread I thought, mass compiling could help. Then only I found the above thread realizing that this behaviour is intrinsic.

Thanks Darren, I never stumbled upon such VI's or probably never checked the error messages when mass compiling.

Herbert

P.S.: Report Generation Toolkit only exists for Windows and LV 8.6 comes with toolkit 1.1.3

[smercurio_fc]

Then please mark Darren's reply as the solution, and not yours. You can unmark a reply as the solution using the "Options" menu.