Leaderboard

I've been using it almost exclusively on all code in our reuse library and several projects from versions 2011, 2012, and 2013. I've had no issues yet. I've also inlined just about all I can in the reuse library as well without incident.

Under Windows there is a special root loop in LabVIEW that registers a LabVIEW Window Class on startup. That supposedly fails when it is already registered and in old days LabVIEW simply passed control to that other instance and then terminated. The allowMultipleInstances ini key is a fairly new addition (well around LabVIEW 7 or so) that seems to make LabVIEW not terminate on RegisterClass() returning an error but instead simply continues. Under Linux there is no such mechanisme and it is even more unusual for an application to not allow being started more than once. They would have to add some internal IPC mechanisme to check for that on startup and I'm sure that never really has come up so far and even a Product Suggestion has a very low chance to ever make it into LabVIEW. allowMultipleInstances most likely is nowhere present in any non-Windows version of LabVIEW. However, at least in Linux (and I suppose on OSX too) you can easily do this by creating a startup shell script for your LabVIEW application and check in there with shell commands for the existence of another instance of the same app. Look here for a fairly simple possibility to do that.

If you installed LabVIEW after DAQmx you will need to re-install DAQmx. But even beyond that you won'd find a version of DAQmx that supports 2009 and 2013 according to this. http://digital.ni.com/public.nsf/allkb/B0D5630C0A50D5C6862578E800459248 In the past a virtual machine (or two real computers) helped with this so that you could have one version of DAQmx with 2009, and another version on a different computer with 2013. You still may run into issues since I'm guessing there are features in the newer DAQmx that aren't in the older. You might just want to develop in 2009 if that is the final form that the code will be in. Going to new versions is easy, going back is more difficult.