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 Ben Johansen - http://www.pcforge.com Authorized Witango & MDaemon Reseller Available for Witango Developement -----Original Message----- From: Bill Downall [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 9:24 AM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: DBMS Action Select with Limit # or Rows What do I do to trace these at the level that would be useful? It's obviously not just the SQL in the Witango debugging output. When I go into ODBC Administrator and "Start Tracing now" using the default odbctrac.dll, and then hit the Oterro database driver through the Witango application, nothing happens. I don't find any results in the \SQL.log file. Thanks. Bill At 03:09 AM 3/10/2004, you wrote: >As this is R:Base specific it may be worth contacting R:Base to see >what is happening in the db/ODBC driver. The issue may lie in the >Oterro 3 driver. 065 introduced a strict ODBC 3.0 interface. 058 >used an ODBC 2 interface to make db calls. Oterro prior to version 3 >only supported ODBC 2.5 calls. Try placing a trace on the db and the >ODBC dm to see what sql it is executing. Are they different? ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
