It may have changed in WiTango 5, but in all versions before that
queryTimeout was only valid in the system scope. You might need to change
it there.
I've used a browser to "batch" jobs like this by selecting a range of
records with the search action and then using a meta equiv="refresh" to
get the next set, if there are any.
On Mon, 20 Jan 2003, David Green wrote:
> I'm working on an app that that searches for a bunch of data and then
> loops through the records inserting them into another table or data
> source. There are approximately 3200 records. So WiTango loops through
> each record... does some manipulation of the data, then inserts it.
>
> The problem is that WiTango dies for some reason. It happens anywhere
> from the 1800th record to the 2800th record. The log file doesn't tell
> me anything. It shows the last insert query, then the next line of the
> file is 'Tango Server started.'. I've run the app 10 times. One worked
> fine and took about 430 seconds to run, the rest all die around 360
> seconds. I change my queryTimeout system variable to 3600 at the
> beginning of the app, then back to 300 at the end. I can't narrow down
> the problem. Does anyone have any ideas or experience something
> similar?
>
> Windows 2000 Advanced Server - IIS 5
> Tango 2000 Standard
>
> Thanks,
>
> David Green
> [EMAIL PROTECTED]
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
>
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
