Windows message when executing VBS
Quote from Matthias Schütte on December 8, 2022, 11:44 pmI call a vbs script within my application with "Call", which takes about 20 to 30 seconds to execute. After about 10 seconds, a window appears regularly with the message: "Script Control: The script you are executing is taking longer than expected to run. Click End to abort the script or Continue to continue script execution."
Is there a way to disable this message?
I call a vbs script within my application with "Call", which takes about 20 to 30 seconds to execute. After about 10 seconds, a window appears regularly with the message: "Script Control: The script you are executing is taking longer than expected to run. Click End to abort the script or Continue to continue script execution."
Is there a way to disable this message?
Quote from luishp on December 9, 2022, 10:27 am@matthias-schutte I think that message is probably not related to VisualNEO.
Does the same script work correctly when executed outside of VisaulNEO?
@matthias-schutte I think that message is probably not related to VisualNEO.
Does the same script work correctly when executed outside of VisaulNEO?
Quote from Matthias Schütte on December 9, 2022, 11:05 amFirst of all, thank you for the quick response to my request. The direct execution of the vbs script remains without a pop-up message. Only the call within VisualNeoWin leads to the message, which is probably triggered by the Windows Scripting Host.
First of all, thank you for the quick response to my request. The direct execution of the vbs script remains without a pop-up message. Only the call within VisualNeoWin leads to the message, which is probably triggered by the Windows Scripting Host.
Quote from Matthias Schütte on December 13, 2022, 1:16 pmI think I solved the problem. The global variable [WSHTimeOut] exists in VisualNeoWin. If the value "-1" is assigned to this variable (SetVar "[WSHTimeOut]" "-1"), the VBS script runs without a message window. I have to admit that I haven't noticed this global variable until now.
I think I solved the problem. The global variable [WSHTimeOut] exists in VisualNeoWin. If the value "-1" is assigned to this variable (SetVar "[WSHTimeOut]" "-1"), the VBS script runs without a message window. I have to admit that I haven't noticed this global variable until now.