Page 1 of 1

Time out in vb-scripts

PostPosted: Sun Feb 08, 2009 3:46 pm
by sombra
I am running a VBscript inside a neobook application. The script works fine, but when the script is handling about 10000 files or more, then a message appear with the next text:

Code: Select all
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.

[ End ]    [ Continue ]

I tried writing: wscript.timeout = 0 inside the script for set an infinite value, but it seems be ignored.
Is there a way for change this behaviour? or... Is it a predefined value in neobook?


PostPosted: Mon Feb 09, 2009 2:36 am
by Horst Helfen
I propose to split your script into smaller parts which process not as many files each.

PostPosted: Mon Feb 09, 2009 5:43 pm
by Neosoft Support
I think that the "wscript" object is only supported for VBScripts that run from a command prompt. Instead you might try one of these:

session.Timeout = 0

server.ScriptTimeout = 0

PostPosted: Sun Mar 29, 2009 2:08 pm
by sombra
Hello Neosoft!

NeoBook v5 Version History.rtf wrote:Added a global variable called [WSHTimeOut] which can be used to modify the timeout value (in seconds)...


This new variable solve the problem commented above. Really, I was wasting many time searching for a solution, but this woks fine in all my tests done.
Thanks again for add this feature and for hear to users.