Hi Ashley,
>> 1) If the process takes an half an hour will the [session] set to a 15 minute expiration time, time out?
No. The client page is refreshing the progress bar, and by doing that acts to keep the session alive. ie the progress-bar-update-request from the browser acts to restart the session timeout countdown.
>> 2.) If the user moves to another web page will this cause any problems?
depends a bit on what you mean. Assuming you mean "in that tab, they lose interest in the process, and move on" then no that won't cause problems. The process will carry on running. (Although it does open the door to the session timing out because the progress update requests will stop.)
>> Seems the progress bar starts were it left off, is this correct?
not really. but not 100% sure what you mean. Usually the variable is reset to 0 when you click the Start button.
>> 3.) How would you stop the process if they clicked the "Start" button and realized they selected the wrong dates?
>> Cancel Button to tell the process through p_web to stop by setting a session value?
yeah, something like that. Set some sort of session value on "Cancel" and then in the source procedure keep an eye on the session value, and just terminate the source procedure.
Cheers
Bruce