Thanks a bazillion Jon, I will try your suggestions! Sean
"Jon Austin" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] You could always improve the whole thing. Try forking out the operation to a background process. :) CFSchedule a shell script to run or something like that. But as a first step trying to debug that problem, add an increased timeout. Because the error is being tranucated and not being caught, something major is being borked and a severe exception is being thrown. Watch the cfstat output too while the op is running. On 7/20/05, Seano <[EMAIL PROTECTED]> wrote: > Where do I start? --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
