No. older versions of the server used to allow request$querytimeout to be assigned, but that is no longer the case in 5.0/5.5
You have 2 options: Assign system$querytimeout - which requires the system password to be set - before, and set it back after Or (my preferred) write your app in a way that it will run for a while, say 10 seconds, and then call itself again and again to continue processing. This will create a system where your server will have a bit of time to breathe between calls, and won't need to abide by any particular timeout. You can also pass the USR and use user variables to manage your workload. Robert -----Original Message----- From: Alan Wolfe [mailto:[EMAIL PROTECTED] Sent: Thursday, July 14, 2005 3:19 PM To: [email protected] Subject: Witango-Talk: running processes in witango that take a long time hey everyone, If you know a certain peice of code is going to take a long time to process, is there a way to change the timeout to a higher value for that request only so that it doesnt timeout half way and only do half of the work? ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
