At 03:46 PM 3/10/2004, you wrote:
There has been a change, if I recall correctly.
Oterro 3.0 is RDEBUG ON.
Chuck Lockwood
Chuck
DEBUG ON worked for me with 3.0. I think the change was the name and
location of the log, from Microrim.log to c:\Oterro.log, as of Oterro
version 2.6.
Bill
-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
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
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
Ben Johansen - http://www.pcforge.com
Authorized Witango & MDaemon Reseller
Available for Witango
-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
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, noth
-Original Message-
From: Bill Downall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 09, 2004 10:38 AM
To: [EMAIL PROTECTED]
Subject: RE: Witango-Talk: DBMS Action Select with Limit # or Rows
A followup:
This definitely was broken in Witango server 5.0 after patch .58 and
before
patch .65. I
Thanks Bill. I thought something was up here.
Steve
-Original Message-
From: Bill Downall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 09, 2004 10:38 AM
To: [EMAIL PROTECTED]
Subject: RE: Witango-Talk: DBMS Action Select with Limit # or Rows
A followup:
This definitely was broken
A followup:
This definitely was broken in Witango server 5.0 after patch .58 and before
patch .65. I have a site still running on .58. A taf that observes the
limit and pages groups of 40 just fine in .58 puts the whole result set on
the page on a server running .65.
I'll send the example taf
Steve,
This is quite weird! I went to look at my taf that does this just fine, and
it doesn't do this just fine anymore!
I have a taf that pages in 50s, and has been working great this way with
next/previous buttons and your configuration as below, except that at the
client site is is Oterro
Steve,
The limit does the following.
It processes the full select and then limits the rows returning.
So if the select returns a 100 rows with the limit, then the limit = 20
prevents the last 80 from returning.
Your are better servered by using the COUNT criteria
Ben Johansen - http://www.pcforg
AM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: DBMS Action Select with Limit # or Rows
Steve,
Are you using the "builders"?
These work fine for me with Oterro 2.6 and 3.0, with the "limit to xx rows"
and "previous xx" and "next xx" links, but I have custom
Steve,
Are you using the "builders"?
These work fine for me with Oterro 2.6 and 3.0, with the "limit to xx rows"
and "previous xx" and "next xx" links, but I have customized the builder
considerably.
Bill
At 11:12 PM 3/8/2004, you wrote:
I am trying to construct a DBMS Select action that will
Steve,
You are probably better doing this with a custom SQL action. What SQL server are you using?
J.
On 09/03/2004, at 3:12 PM, Fogelson, Steve wrote:
I am trying to construct a DBMS Select action that will limit the number of
rows retrieved.
WITH IMAGINATION
Planning, Implementation and Ma
14 matches
Mail list logo
