Yah, I'd thought of the pre-search but hate to have to add all those in;
might as well just rewrite them all as Search Actions.  I'll have to
think about the on-the-fly criteria calculations, but I can see how that
might work.

Thanks for the advice!  

jamileh

> -----Original Message-----
> From: Robert Shubert [mailto:[EMAIL PROTECTED] 
> Sent: Friday, December 12, 2003 4:32 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Witango-Talk: Paged results for a Direct DBMS action
> 
> 
> You'll either have to pre-search for the total records 
> available (without your subset code) and save that in a 
> variable to replicate what <@TOTALROWS> does. Or you'll have 
> to calculate what your next and previous subset criteria are 
> on the fly for each button to work.
> 
> -----Original Message-----
> From: Wilcox, Jamileh (HSC) [mailto:[EMAIL PROTECTED] 
> Sent: Friday, December 12, 2003 5:10 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Witango-Talk: Paged results for a Direct DBMS action
> 
> Each Direct DBMS queries for a specific subset of records.  
> All of those records are then displayed in the resultsHTML.  
> I need to add next/previous paging to those displayed rows.
> 
> > -----Original Message-----
> > From: Robert Shubert [mailto:[EMAIL PROTECTED]
> > Sent: Friday, December 12, 2003 4:08 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Witango-Talk: Paged results for a Direct DBMS action
> > 
> > 
> > I think this depends on how you are handling the selection of
> > the subset of records. Does your Direct DBMS actually bring 
> > all records back and then filter in the resultsHTML, or do 
> > you limit the database's response?
> > 
> > Robert
> > 
> > 
> > -----Original Message-----
> > From: Wilcox, Jamileh (HSC) [mailto:[EMAIL PROTECTED]
> > Sent: Friday, December 12, 2003 4:53 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Witango-Talk: Paged results for a Direct DBMS action
> > 
> > Yah, I can probably rewrite the queries to run in Search
> > Actions, I'm honestly not sure why they're set up as Direct 
> > DBMS.  However, the page has a fair list of different queries 
> > in the menu & with slightly different output for each, so I 
> > was hoping to avoid rewriting them all. I suppose I could 
> > look on this as an opportunity to clean up some code; I may 
> > be able to set it up with one or two queries and use 
> > variables in the menus.  :/
> > 
> > I didn't realize until I was messing with this that the
> > Search Action seems to collect a fair bit of query info that 
> > the Direct DBMS Action doesn't; I'm not sure when or how it's 
> > collected, nor where it's hiding. Behind-the-scenes magic, 
> I guess.  
> > 
> >  
> > 
> > > -----Original Message-----
> > > From: Jim Kass [mailto:[EMAIL PROTECTED]
> > > Sent: Friday, December 12, 2003 3:45 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: RE: Witango-Talk: Paged results for a Direct DBMS action
> > > 
> > > 
> > > 
> > > 
> > > The DBMS Action has no knowledge about your query... and thus it 
> > > cannot get row# information or totalrows (which is used in the 
> > > manual's implementation of next/prev results).
> > > 
> > > However, depending on how complex your DBMS Action, you 
> can use the 
> > > Search Action with custom criteria and results... and you can 
> > > probably accomplish the same query and still use the pre-fab 
> > > next/prev code.
> > > 
> > > Just a suggestion.
> > > 
> > > Jim Kass
> > > Web Developer
> > > 
> > > --
> > > Forestweb: The Source for Industry Intelligence
> > > Best Content -- Most Relevant -- Best Delivery 
> > > http://www.forestweb.com
> > > (310) 553 - 0008
> > > 
> > > -----Original Message-----
> > > From: Wilcox, Jamileh (HSC) [mailto:[EMAIL PROTECTED]
> > > Sent: Friday, December 12, 2003 1:31 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Witango-Talk: Paged results for a Direct DBMS action
> > > 
> > > 
> > > OK, I need to add next/previous paging to a webpage.  This is the 
> > > results page of a direct dbms action.
> > > 
> > > The paging in the manual doesn't work, because it is 
> based on having 
> > > checked the "Get Total Number of Matching Rows" box in 
> the Results 
> > > tab of the Search Action.
> > > 
> > > The Direct DBMS Results tab doesn't have that option, I dunno why.
> > > 
> > > Has anyone done this?
> > > 
> > > Thanks.     j
> > > ______________________________________________________________
> > > __________
> > > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
> > > 
> > > ______________________________________________________________
> > > __________
> > > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
> > > 
> > ______________________________________________________________
> > __________
> > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
> > 
> > ______________________________________________________________
> > __________
> > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
> > 
> ______________________________________________________________
> __________
> TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
> 
> ______________________________________________________________
> __________
> TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
> 
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf

Reply via email to