Why is MAX tied to LabVIEW when uninstalling

[GregFreeman]

After still having problems with MAX, seen here, I wanted to uninstall just MAX and the drivers so I could reinstall the 2009 MAX and drivers (since those work). Why do I have to uninstall LabVIEW in order to uninstall MAX? I understand they are "tied together" but what is it behind the seens that makes LabVIEW dependent on MAX to the point LabVIEW can't run without it? 3 hours of my time down the drain again.

[GregFreeman]

seens....i think i meant scenes

[pallen]

I feel your pain here. 

In fact I was debating whether or not to make some kind of post documenting the "interesting" experience I had yesterday.

Basically a customer had PC power off during testing due to a power outage.  After that, DAQ wouldn't work and their application threw errors. 

They tried uninstalling and reinstalling the DAQ drivers. ( Including MAX )  But that didn't help.

When I worked on it yesterday, I used MSI Blast on it.  Rebooted.  Then reinstalled the DAQ drivers.  That's when I started getting the "Could not connect to database" error. 

I was happy there was not only information, but an actual program I could run to address this issue.  I didn't have a lot of hope for it considering I had blown away everything NI on the machine and there was still an error.  Fortunately it did work.  But I'm a little confused as to why.  Everything should have just worked on full reinstall like I did.  But somehow, something corrupt was still left behind.  (Or so it seems)

I have learned over the years though that uninstalling anything can have unwanted results.  Messing with one version of LabVIEW on a given PC can definitely effect the other versions of LabVIEW on that PC.