Use of Environment Variables in Scripting
I am testing your use of environment variables in scripts using your BETA 4.1.4 version. When I launch the script from the inside the COMMAND.EXE window, it works fine - successfully replacing the environment variable with the actual file name stored in the system's environment. But when I launch the CMD EXEC from Microsoft SQL's job handler with the same command string, the environment variable (in the form %ENV%) does not get replaced with the stored fiel name. I have captured the logs in both occasions and that is the only difference. When I run it from SQL, it is acting like version 3 and attempts to retrieve a file named %ENV%.