environment variable problem

[jamesa]

Hallo,

I wrote a function to propagate the environment variable as recommended in the MSDN article Q104011

It worked fine. I could later on see the variable on the shell using set.

I wrote another function to get the environment variable. Curiously, I can get back the new propagated environment variable.

Dim strMyNewVar as String
Dim strVariable as String
Dim objWSH
Set objWSH = CreateObject("WScript.Shell")


strMyNewVar = “%MyNewVar%”

strVariable = objWSH.ExpandEnvironmentStrings(strVariable)
    
Debug.Print strVariable '(give nothing)

Am I doing something wrong?

[malleyo]

I'm not familiar with this at all, but something I noticed was:

Dim strMyNewVar as String
Dim strVariable as String
Dim objWSH
Set objWSH = CreateObject("WScript.Shell")


strMyNewVar = “%MyNewVar%”

strVariable = objWSH.ExpandEnvironmentStrings(strVariable) '<-- Should this be strMyNewVar ?
    
Debug.Print strVariable '(give nothing)

Since you just declared strVariable, it's passing an empty string to ExpandEnvironmentStrings.

[Comintern]

This was in the MSDN article you reference, my bold added:

However, note that modifications to the environment variables do not result in immediate change. For example, if you start another Command Prompt after making the changes, the environment variables will reflect the previous (not the current) values. The changes do not take effect until you log off and then log back on.

To effect these changes without having to log off, broadcast a WM_SETTINGCHANGE message to all windows in the system, so that any interested applications (such as Program Manager, Task Manager, Control Panel, and so forth) can perform an update.

[jamesa]

Hallo Comintern,

thanks a lot for responding.

You forgot to read in detail my original post that rfefers to the MSDN article Q104011.


Hi malleyo,

you are wright with your notice. it was a type mistake. But that was not the probleme.

The think was that I started vb before propagate the setting change.


Thanks