Considerations for CRT Environment variables

Description: When updating the program, two tabs were opened AB, in the a tag to modify environment variables, add new jar package.
Then source. The B-Tag executes a timed program that throws a run-time error that the class cannot find.

Finally, two labels are opened and the environment variables are modified, but the two tags show different environment variables.

"When LabVIEW starts, msvcrt7.1 and msvcrt9.0 are simultaneously load into memory. They all read the current LabVIEW environment variable and put it into their global variables. When we first set up the process environment variable and then load the XILINX DLL from LabVIEW, the Windows loader discovers that msvcrt7.1 has been loaded into memory and therefore no longer load, so we use setenvironmentvariable () The environment variables set are not updated in msvcrt7.1, so Xilinx DLLs have no way of being read out. "

Simply put, an open label page does not synchronize environment variables with the system in real time.

Therefore, after you use CRT label A to modify the environment variables, you can only use a tag execution program or the newly opened tag execution.

Considerations for CRT Environment variables