03-16-2016 02:25 PM
Not a big deal but thought this was a little strange. I was surprised by an Excel report problem where all of a sudden LV didn't act like it was running as under an administrator when it should have been. I went back and checked and sure enough it wasn't. I didn't do anything to it's privileges or anything else with this computer and nobody else touches it. All I've done is debug a LV program. How does a program stop running as under an administrator without anyone doing anything to it? Is there a "run as administrator" property that I need to set in the program to prevent this from happening in the completed application?
03-16-2016 05:17 PM - edited 03-16-2016 05:18 PM
I am not sure I have ever needed LabVIEW to run "as administrator", in fact it caused problems once when someone adjusted the UAC so command prompt windows were always opened "as administrator". So using systemexec LabVIEW could open a command prompt window but then did not have the rights to close it. Leaving behind a bunch of command prompt windows. My soultion was not to run LabVIEW 'as administrator' but to set UAC back to a "standard" level.
What are you doing to require LabVIEW or LV executable to run "as administrator"?
03-17-2016 09:14 AM
@RTSLVU wrote:I am not sure I have ever needed LabVIEW to run "as administrator", in fact it caused problems once when someone adjusted the UAC so command prompt windows were always opened "as administrator". So using systemexec LabVIEW could open a command prompt window but then did not have the rights to close it. Leaving behind a bunch of command prompt windows. My soultion was not to run LabVIEW 'as administrator' but to set UAC back to a "standard" level.
What are you doing to require LabVIEW or LV executable to run "as administrator"?
This was exactly my experience as well.