ok. I'd still be concerned that if a user is having vbs execution issues, that activex scripting might have the same issues.
yep – quite likely
I had started a test app yesterday to try running octave from it with also settings env vars but got to the point where it would start octave-gui.exe – either hidden (but then cant get to the GUI) or not hidden(at which point it flashed a couple of console screens on loading)
I ran out of time at that point for seeing alternative way of doing the start part that worked.
I guess need to wrk out what the vbs script is really doing when it calls wshShell.Run, as that seems to work