However, every once in a while, a mistake is made in creating the report template in the Builder and when CFREPORT is executed against the template CFREPORT appears to go into run away mode. In an attempt to kill the process people click the back button or X to kill the browser. This is OK except that JRUN is now running amuck doing whatever it was doing.
My question; Is there a way to wrap a timeout or cftry/cfcatch pair around CFREPORT to just kill it after some predetermined time, advise the user and then go to another page without causing JRUN to run amuck?
The Timeout parameter in CFREPORT does not apply because we are not using Crystal Reports.