I have a script that takes quite a while to execute, creating perhaps hundreds of records from text pasted by the user. At times the process takes so long that the user's session in the web browser times out. Is there a common workaround for this when interacting with a database via IWP? I tried refreshing the window periodically, but that seems to have no effect. I thought of briefly pausing the script periodically, but that's not compatible with IWP. The procedure is successful when the user logs in again, but the timeout is unacceptable.

Thanks,

Chuck

I've worked with some big-iron finance systems whereby reports are created as batch jobs: set the batch parameters, get the process going, then come back later to see how it's done.

This might solve the timeout problem by avoiding it completely.

I did think of something like that, but the user wants to have the feedback that the job is done and be able to navigate through the imported data.

I understand that a workaround may have to compromise, but I'm hoping that the basic interface of beginning the task and immediately seeing when it's complete can be kept.

Thanks,

Chuck