Hi Ted,
Are you using the "Limit to" and "Start retrieval at row number" properties
of the Search Action to manage your output in chucks of 100 records?
If so, you should know that these settings are for communicating with your
ODBC Database Driver, and not with the Database directly.
If there i
actualy Ted, i bet when you use paging lets say you want records 10,000 to
10,100 results, i think it has to "qualify" all the results up to 10,000
even though you only get the 100 records.
if you think about it like if i tell you to grab all books from the library
where the authors name contains
Witango is taking the results and placing them in a variable (file on
server) and then starting at 1 counting to 100 and sending that to the
browser. This works very quickly, but as you get farther away from
record 1 it takes longer to sequentially count down the file.
Ben Johansen - http://www.pc
I have found the same result as Ben when using the search builder. In
fact, if you turn debug on you can see the variables being loaded.
If you have 500 items and list only 2 per page, then start scrolling
through the pages, you will notice that the variable
local$search_vals_HTML keeps appendi
AIL PROTECTED]
> Sent: Monday, July 28, 2003 2:55 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Witango-Talk: Search reterivial follow up
>
>
> I have found the same result as Ben when using the search builder. In
> fact, if you turn debug on you can see the variables being loaded.
-
From: "Scott Cadillac" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 28, 2003 10:35 PM
Subject: RE: Witango-Talk: Search reterivial follow up
D'oh!
Thanks Dude. I think you and Ben are correct, and I'm just remembering my
facts wrong.
It was
in the
Limit To: box on the Results tab in the Search Action.
Ted
-Original Message-
From: Web Dude [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2003 4:55 PM
To: [EMAIL PROTECTED]
Subject: RE: Witango-Talk: Search reterivial follow up
I have found the same result as Ben when
Title: Re: Witango-Talk: Search reterivial follow up
Try changing the function to _function. The logic of the builder relies on the ability to strip the args that start with _
If you look at the logic that builds the search arg logic you will see the section:
<@ROWS ARRAY=arg_na
Title: Message
I am
already using _function. The code looks just like
below.
[Ted Wolfley]
-Original
Message-From: Witango Customer Support
[mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003
8:19 AMTo: [EMAIL PROTECTED]Subject: Re:
Witango-Talk: Search reterivial follow
If you look at the name of the hidden field it seems to be picking up
³function² from somewhere.
Where is the search arg function coming from?
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
The was from me on
a different post. I always wondered if there was a reason for the "_"
in the builders. Unfortunately, almost everything I built by hand is
using function instead of _function. I guess I will probably just
change the tafs where this seems to be an issue.
If you look at the
11 matches
Mail list logo
