Re: [URL] around a [sendmail] recipient? - SEARCHING: command vs. context

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 28010
interpreted = N
texte = >The reason I switched to a command-based search is because I want the user to input a date range which is used to limit the records found to those with a date field within that range. Upon submit it goes to the page that display the [founditems]. But when I tried doing that with the [search] context on the display page itself (instead of command), then I couldn't seem to get the [shownext]s to work right. The [search] context was something like-[search db=some.db&mrDayOrdereddata=[userinput1]&xrDayOrdereddata=[userinput2]...&max=5] which worked for the first batch of 5, but the shownext links for the other batches of 5 didn't work right. I understand that for shownext to work right it requires that all the search params be present in the initial search. No how I can do this while using a [search] context instead of command?-John> > > I would stop using commands if I were you, it simplifies things and makes everything more secure if you *ALWAYS* use contexts. There are things you simply cannot do witout using a context -- such as [url]ing a form value when that form is doing a command-based search for example, so just make a habit of always using contexts and life will be a lot easier for you ... :) > ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Associated Messages, from the most recent to the oldest:

    
  1. Re: [URL] around a [sendmail] recipient? - SEARCHING: command vs. context (John Butler 2000)
>The reason I switched to a command-based search is because I want the user to input a date range which is used to limit the records found to those with a date field within that range. Upon submit it goes to the page that display the [founditems]. But when I tried doing that with the [search] context on the display page itself (instead of command), then I couldn't seem to get the [shownext]s to work right. The [search] context was something like-[search db=some.db&mrDayOrdereddata=[userinput1]&xrDayOrdereddata=[userinput2]...&max=5] which worked for the first batch of 5, but the shownext links for the other batches of 5 didn't work right. I understand that for shownext to work right it requires that all the search params be present in the initial search. No how I can do this while using a [search] context instead of command?-John> > > I would stop using commands if I were you, it simplifies things and makes everything more secure if you *ALWAYS* use contexts. There are things you simply cannot do witout using a context -- such as [url]ing a form value when that form is doing a command-based search for example, so just make a habit of always using contexts and life will be a lot easier for you ... :) > ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to John Butler

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

did I miss anything (1997) Checking two required fields (1998) Search Context: How to set Max=N? (2000) ReturnRaw, download link for mov (2007) Nested tags count question (1997) Webcat 2.0.1 date math bug -> Crash! (1997) Logging purchases (1997) Grep and removing text (2002) Validating A Date (2004) using showpage and showcart commands (1996) HELP - NONE STOP DIGESTS. Digest for 4/24/97) (1997) form image (2000) New One (for me).... Error type 12 (1999) PIXO with cometsite ... and/or other plugins (1998) multiple product databases (1997) PCS Frames (1997) WebCat2b13MacPlugIn - More limits on [include] (1997) [NT] ie 4.0 required (1997) Dates - Search and Sorting (1999) security (1997)