>You want access to whatever internal structures the cfmx runtime uses to track the various data points needed for the debugging output.
Maybe. I'm not entirely sure what you mean, but it sounds about right ;-) I just think - on long processes - it might be more useful to see some of the debugging stuff as it happens, rather than after it happens. Given CF has the stuff "in there somewhere", I was wondering if it was possible to liberate it. -- Adam This email contains confidential information. If you are not the intended recipient of this email, please notify Straker Interactive and delete the email. You are not entitled to use it in any way. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org
