08-02-2007 06:36 PM
I am upgrading from LV8.0 to LV8.2.1. After the SW install completed, all of my top level vi’s are broken. I have two main issues so far. There may be more but with all top level vi’s broken I don’t have any visibility.
1) When I did a mass compile on my first project folder I got over 700 “### Bad VI” entries! This project is only moderate in size, maybe 500 vi’s. When I looked into a couple of the vi’s to see what was wrong, it appeared in each case the 8.2.1 subvi was not compatible with the 8.0 subvi. One example is in the report generation tools. I no longer have the excel or word options in the New Report.vi even though the “LabVIEW Report Generation Toolkit for Microsoft Office” utility is still installed. How can I regain my ability to write excel and word docs? Also, the Dispose Report.vi no longer has save options. Will open files be saved and closed before the vi terminates or do I need to add more code to do this?
2) I had customized my Functions and Control pallets with special driver libraries. I am using the .lvlib constructs to load application specific drivers. The pallets are now reset to default. Is there a way to preserve the pallet configuration during upgrades? This can’t be all that difficult.
Backwards compatibility and preserving user configurations are both hallmarks of good programming practices. Surely you are not going to force me to repair 50 vi’s per project and reconfigure my pallets every time I do an upgrade. There must be a better solution. Any advice would be appreciated.
Bob
08-02-2007 08:47 PM