Project cannot find Stop Task.vi

[NIerrors]

First off I have LabVIEW 2013SP1 and 2014 installed on Windows 7. I do not understand why National Instruments keeps mulitple versions of their software on a computer each time you upgrade, but here is my problem.

I created a project in which I created a couple of excutables. Everything was going good. I was then looking into a way to save the scales with the excutable so I created an installer. Everything looked good. the excutable works. Now on the original computer I open the project hoping to edit the vi to make a new excutable, and it cannot find anything.

When I attempt to open a VI in the project it starts searching for files. It cannot find DAQmx Clear Task.vi, DAQmx Stop Task.vi, Convert 1DWfm to DDT.vi, DAQmx Read (Analog 1D Wfm NChan NSamp).vi, DAQmx Read.vi, DAQmx Start Task.vi, DAQmx Timing (Sample Clock).vi, DAQmx Timing.vi, DAQmx Create Channel(AI-Temperature-Thermocouple).vi, DAQmx Create Channel (TEDS-AI-Temperature-Thermcouple).vi, DAQmx Create Channel(AI-Voltage-Basic).vi, DAQmx create Channel (TEDS-AI-Basic).vi, DAQmx Create Virtual Channel.vi, and DAQmx Create Task.vi.

After this, it opens the VI. It states a warning that a driver or toolkit component is not found. MIssing resource file "daqmx.rc". Where is this located? How do I load it? Why all of a sudden are these items missing when this was the computer I created project with?

I have reinstalled the 2014 after this, but noticed an issue installed the driver disc. I did NOT uninstall the software. Do you feel this is required, start from scratch?

Any help is clearly appreciated.

[Dennis_Knutson]

First, you are the one keeping multiple versions. If you don't want an older version, uninstall it.

Second, after installing LabVIEW, you must install the appropriate device drivers after. For DAQmx, you need at least version 14. What does MAX say? What issue do you have with the device driver disc?

[crossrulz]

Install the latest DAQmx on the development computers.  It is that simple.  Part of the driver install is the LabVIEW XXXX Support.  So you need to make sure you install the drivers after you install LabVIEW.

[NIerrors]

First, I was just explaining that I have multiple versions of LabVIEW on the computer. Most software companies uninstall the previous version when you update.

Second, I just installed the Driver's CD, and still no found files. My biggest questions is how did this happen. Everything was fine, and I made no updates. I will review that DAQmx, I believe that was on the Driver's Cd.

[NIerrors]

Not sure what happened, but it is resolved. DAQmx must have gotten corrupted somehow. The third time I installed the Driver's Cd it went through, and the problem resolved itself.

[NIquist]

A programming language is not like a browser or other software that gets updated.  Most of us would be VERY upset if installing a newer version wiped out all older versions we might still be using to support legacy code.  LabVIEW is actually quite good these days at co-existing peacfully with other versions, but you do have to make sure each version has its required packages and that they get installed in the proper sequence.  Not quite sure why you had issues with your install but it happens occasionally.   Glad you got it worked out.  

[natasftw]

First, you were complaining about something that works as expected.  There is benefit to being able to switch between versions of LabVIEW.  In fact, there's use to switch between LabVIEW 2014 (32-bit) and LabVIEW 2014 (64-bit).  If it functioned as you suggested, you'd require multiple development machines or getting used to uninstalling/reinstalling each time you wanted to work in a different environment.  When you start programming more, you'll understand the value.  What you're doing right now is similar to a beginner programmer complaining about functions.  "I don't understand why these exist.  I can just write everything in main."  With experience, you'll understand why the complaint simply doesn't make sense.  When you upgrade your Quicktime, you add functionality without removing functionality.  That's why it writes over the other installer.  When you update your DAQmx drivers, they write over the old installation.  When it makes sense to do so, NI will write over your old installation.

Second, it didn't fix itself.  You fixed it.  You installed the drivers.  That's not fixing itself.