Hello,
I have an updater in my app, which makes under Vista the file update with VBScript because of the UAC. My updater works in most cases fine. But I have a certain number of Vista customers, where It doesn't work at all and I am not yet behind, what is going on there. The updater just runs through without any error message. The nasty thing is I don't get any error back from VBScript to my app, so that my app states that the update was made successfully, though it wasn't. My questions are not going to my code, but to some principles with calling the shell wscript.exe 1. I tried to catch any error from the get shell() command with "the result", "the syserror", "try -catch", but got never any error back from the shell, even if I have a wrong syntax in the VB, where the VB fails, the rev doesn't gets noticed. Which is the correct way to catch an error from a VBScript on the shell? 2. Do I have to return explicity any error from the script back to rev, or will they passed to rev anyway? If yes, how and where? 4. Are there any experiences of windows installations without the scripting host? Perhaps the Home edition? If yes, how to check for that? 5. If every Vista version should have the windows scripting host, can it somehow be deactivated, so that my updater runs without result? If yes, how? 6. If the user clicks "cancel" while Vista is asking to allow this process, how can I get aware of this "cancel" in my rev app? Is there a chance to catch a "cancel" down from Vista level in my rev app? 7. Are you aware of any other VBScript gotchas? Thanks for sharing any experience Tiemo _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
