Hey John, yes i have noticed this when i have user or domain scope tcf's and here's the problem..
if you create a tcf and store it in a domain variable, then turn on debugging for that taf and clear the cache (if you have cacheing on), before debugging info will show up, you need to re-create the domain variable holding the tcf because until you do that, it will still be the OLD tcf stored in the variable - which has debugging off. Rober's suggestion of forcing debugmode on across the board should be able to get you what you want though more easily (: On 8/4/05, Robert Shubert <[EMAIL PROTECTED]> wrote: > Do you get the same result if you set user$debugmode = forceon ? > > -----Original Message----- > From: John McGowan [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 04, 2005 12:37 PM > To: [email protected] > Subject: Witango-Talk: Witango 5.5. Debugging Output Now Showing Some > Queries > > Anybody notice an issue with 5.5. server not showing all the debugging > information for certain actions. I turn on debugging in an instance of > a tcf and expect to see all the Action information including SQL > generated and changed variables, but it doesn't all show up anymore... > It always showed up fine in 5.0 > > Insights? > > /John > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
