Frequently Asked Questions

1. Why do you abbreviate DataAct Version Chooser as LVC?

   1. Answer:  The DataAct Version Chooser for LabVIEW was originally called "LabVIEW Version Chooser" hence LVC, however LabVIEW is a trademark of National Instruments and it is illegal (and wrong) to use any trademarked name in a product title.

2. Why does LVC open files in the last LabVIEW version launched instead of my selection when there is more than one LabVIEW application running?

   1. Answer:  It appears that LabVIEW.exe uses DDE to see if it is already running, so even though LVC tries to launch LabVIEW version A, when version A starts it actually calls the last version that was launched.  This can be verified by starting LabVIEW version A (use either Start Menu shortcut or double click the actual LabVIEW.exe from explorer) and then do the same with LabVIEW version B.  Now go back and try version A, you will get version B!

3. Why does LVC no longer start when I double click on a LabVIEW file?

   1. Answer:  This can occur if the LabVIEW file extensions were re-registered to LabVIEW.  Possible causes of the re-registering could be from installing or reinstalling LabVIEW, running an application with the run time engine that is set to register extensions, or using a different LabVIEW preference file with the -pref switch.  To correct this problem either run the Maintenance Wizard with the Repair option or reinstall LVC.

4. Why does LVC OPEN the LabVIEW file itself and then open it in the LabVIEW version I chose?

   1. Answer:  This can occur if the ddeexec registry keys are enabled in the registry.  Possible causes of this can be if you use the Windows Explorer:Tools:Folder Options:File Types to modify a LabVIEW file type action and enable the "Use DDE" option.  To correct this problem delete the ddeexec keys from the registry OR either run the Maintenance Wizard with the Repair option or reinstall LVC.

5. LVC is a really useful application, can I add my own actions?

   1. Answer:  The short answer is no with this release.  However the next major release is going to allow for a plug-in architecture.  Here are some of the other actions that are under consideration:

      -LLB to Directory
      -Mass Compile
      -Print
      -Specify different preference file

      If you don't see the action that you want either send a request or wait until the next major release and build it yourself.

6. I want to check the version of multiple files, how can I do this with LVC?

   1. Answer:  Currently you can only use the "Get Version" action on one file at a time.  However, to save time with checking multiple files try the Drag and Drop Interface.

7. I want to get the version of an executable that created with LabVIEW, how can I do this with LVC?

   1. Answer:  Since an executable doesn't have a LabVIEW file extension, the "Get Version" action will not be available from the context menu.  If the executable uses a data.llb file then you use "Get Version" on the library to get the executable's version or use the Drag and Drop Interface.

8. Why does LVC only return one version from a library file (*.llb)?

   1. Answer:  LVC currently returns the version of the first file in a library as the version for the library.  Planned feature is to show the versions of every file* inside of a library and allow the selection of which file to open.

      *FYI...You can save LabVIEW files of different versions inside the same library!

9. LVC has a great installer, what tools were used to create it?

   1. The installer/maintenance wizard was created using NSIS (Nullsoft Scriptable Install System).  It is released under an open source license and is completely free for any use.  More information can be found at http://nsis.sourceforge.net/