I don't know the particulars of these scripts, but 2 things:
1) When you "shell out" of an application you're creating a separate
shell process below the current one which inherits the environment of
the creator. Any changes you make to the environment in the sub-shell
are not propagated back to the parent shell.
2) Most applications, when first invoked, copy the state of
environment variables to some internal structure. So even if you
could change the environment variables in your own process, it
wouldn't change the copy your application (UniData in this case) is
using.
I suspect you're being tripped up by one or both of the above.
Now, if you're executing your scripts *before* starting the UniData
process, I don't know what's wrong.
Good luck!
Stewart
-----Original Message-----
From: Ron Sharcott <[EMAIL PROTECTED]>
Date: Thu, 30 Mar 2006 08:09:59 -0800
I can't believe this. The results I'm getting are showing UniData only
allowing a shell for the environment variable and won't allow it to be
sourced.
...
Ron Sharcott (3635)
--
Stewart Leicester | JenSoft Technologies, LLC
"Per Ardua Ad Astra" | <mailto:[EMAIL PROTECTED]>
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
