There has been a change, if I recall correctly. Oterro 3.0 is RDEBUG ON.
Chuck Lockwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ LockData Technologies, Inc. 309 Main Avenue, Hawley, Pa 18428 570-226-7340 ~ Fax: 570-226-7341 [EMAIL PROTECTED] ~ www.lockdata.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -----Original Message----- From: Bill Downall [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 2:21 PM To: [EMAIL PROTECTED] Subject: RE: Witango-Talk: DBMS Action Select with Limit # or Rows Ben, Actually, it turns out that Oterro DOES log to the odbc log, it just doesn't show up until you disconnect. I had two 6 Megabyte logs from 2 queries, one was the odbc administrator SQL.log, the other was the Oterro debug oterro.log. Similar details, but slightly different format. No wonder performance took a big hit! At 10:16 AM 3/10/2004, you wrote: >Bill Oterro doesn't log to the ODBC Log. > >You need to do this: > >Add the line: >DEBUG ON >to the Oterro.cfg file. >This will create an Oterro.log file in the C:\ directory ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
