LabVIEW 7.0 Readme for Windows

April 2003

This file contains important last-minute information about LabVIEW 7.0 for Windows, including installation and upgrade issues, compatibility issues, and changes from LabVIEW 6.1. Refer to the LabVIEW Upgrade Notes for more information about upgrade and compatibility issues and for a complete list of new features in LabVIEW 7.0. Refer to the LabVIEW Release Notes for installation instructions. You can access both of these documents by selecting Help»Search the LabVIEW Bookshelf in LabVIEW.

Refer to the National Instruments Web site for the latest information about LabVIEW 7.0.

Upgrading from Previous Versions of LabVIEW

  • Some example VIs take advantage of functionality that is not available in the LabVIEW Base Package. If you have the Base Package, you might receive errors when you mass compile these VIs. Typically, these VIs use analysis VIs or the picture control.

Known Issues

  • To use Windows Explorer to display or modify the contents of .llb files, you must have Internet Explorer 5.5 or later.
  • .NET does not provide constructors for basic data types like numeric. If you encounter a property or a method parameter that accepts System.Object and you want to wire a numeric to it, use the To Object VI in the vi.lib\Platform\dotnet.llb. This VI explicitly converts a LabVIEW data type to a .NET object.
  • Typically, LabVIEW converts a .NET object to a known LabVIEW type. However, in some cases where a property or a method returns an abstract class such as System.Object or System.Array, you might want to explicitly convert them to a LabVIEW type using the To Variant VI in the vi.lib\Platform\dotnet.llb. You then can use the Variant To Data function to cast the variant to typed LabVIEW data.
  • When you compare two VIs by selecting Tools»Compare»Compare VIs, LabVIEW does not compare Express VIs on the block diagrams of the two VIs. LabVIEW always lists Express VIs as differences in the Differences window.
  • When you run a TestStand 1.x/2.x operator interface VI a second time after running the VI once and stopping it, you might receive error –2147467259 from the Automation Open function that attempts to open the TestStand Engine. The error occurs because of a change in the default threading configuration of LabVIEW 7.0 that is incompatible with the behavior of TestStand 1.x/2.x. This error does not occur with later releases of TestStand. To correct this error, add the following line to the labview.ini file in the labview directory:

    ESys.StdNParallel=1

    You must restart LabVIEW after you make this change for the change to take effect. If you make this change, LabVIEW will have only one thread per execution system. As a result, your application might not perform as well as it could under LabVIEW 7.0, and the degraded level of performance might approach levels in LabVIEW 6.1.

Documentation

  • According to the LabVIEW User Manual and the LabVIEW Quick Reference Card, the default value for the path data type is Not a Path. According to the LabVIEW Help, the default value is an empty path. The LabVIEW Help is correct.
  • In the LabVIEW Upgrade Notes, the Converting Datalog Files section is located under the Upgrading from LabVIEW 5.x section. The Converting Datalog Files section should be located under the Upgrading from LabVIEW 6.x section.

© 2003 National Instruments Corporation. All rights reserved.