Re: Data Type Search Problem

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 56006
interpreted = N
texte = No. [txtKeyword] is the textbox for the user's keywords. Then they press = the search button. After that, a data table is created with html and = populated by the search results. My actual search string is a lot longer = than this and acts just fine besides the end_date being of type date. = That is messing everything up because sometimes end_date is zero instead = of an actual date. I need a workaround for end_datetype=3Ddate. If end_date always contained = a date then it would work fine (I tried) but I need to account for end_= date being never. Thanks. Justin Carroll On Wednesday, March 31, 1943, Gary Krockover = wrote: >Is [txtKeyword] always inputted from the user as a number? > >"&wsmy_heightdata=3D[txtKeyword]" and >"&my_heighttype=3Dnum" > >Should any of those fields be "required" as well, as in=20 >&wsmy_namedataRQ=3D[txtKeyword]? > >GK > > > > >At 12:51 PM 2/10/2004, you wrote: >>An example of my search would be this: >>[search=20 >>db=3Ddatabase.db&wsmy_namedata=3D[txtKeyword]&wsmy_heightdata=3D[= txtKeyword]&wsend_datedata=3D[txtKeyword]&my_heighttype=3Dnum&my_= heightsdir=3Dde&end_datetype=3Ddate&end_datesdir=3Dde] >> >>I actually have two headers for a date, start_date and end_date. The=20 >>start_date works fine because it always has a true date in it (xx/xx/= xxxx)=20 >>but my end_date, like I said, sometimes contains a 0 so end_= datetype=3Ddate=20 >>messes the whole search up - makes it act strange by pulling every = record=20 >>for anything in [txtKeyword]. >> >>Maybe I shouldn't have a zero for no end date. Should it be blank? = Thanks. >> >>Justin Carroll > > >------------------------------------------------------------- >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 >Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- 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 Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Data Type Search Problem ( Justin Carroll 2004)
  2. Re: Data Type Search Problem ( Glenn Busbin 2004)
  3. Re: Data Type Search Problem ( Justin Carroll 2004)
  4. Re: Data Type Search Problem ( Donovan Brooke 2004)
  5. Re: Data Type Search Problem ( Justin Carroll 2004)
  6. Re: Data Type Search Problem ( Gary Krockover 2004)
  7. Re: Data Type Search Problem ( Justin Carroll 2004)
  8. Re: Data Type Search Problem ( Donovan Brooke 2004)
  9. Re: Data Type Search Problem ( Donovan Brooke 2004)
  10. Data Type Search Problem ( Justin Carroll 2004)
No. [txtKeyword] is the textbox for the user's keywords. Then they press = the search button. After that, a data table is created with html and = populated by the search results. My actual search string is a lot longer = than this and acts just fine besides the end_date being of type date. = That is messing everything up because sometimes end_date is zero instead = of an actual date. I need a workaround for end_datetype=3Ddate. If end_date always contained = a date then it would work fine (I tried) but I need to account for end_= date being never. Thanks. Justin Carroll On Wednesday, March 31, 1943, Gary Krockover = wrote: >Is [txtKeyword] always inputted from the user as a number? > >"&wsmy_heightdata=3D[txtKeyword]" and >"&my_heighttype=3Dnum" > >Should any of those fields be "required" as well, as in=20 >&wsmy_namedataRQ=3D[txtKeyword]? > >GK > > > > >At 12:51 PM 2/10/2004, you wrote: >>An example of my search would be this: >>[search=20 >>db=3Ddatabase.db&wsmy_namedata=3D[txtKeyword]&wsmy_heightdata=3D[= txtKeyword]&wsend_datedata=3D[txtKeyword]&my_heighttype=3Dnum&my_= heightsdir=3Dde&end_datetype=3Ddate&end_datesdir=3Dde] >> >>I actually have two headers for a date, start_date and end_date. The=20 >>start_date works fine because it always has a true date in it (xx/xx/= xxxx)=20 >>but my end_date, like I said, sometimes contains a 0 so end_= datetype=3Ddate=20 >>messes the whole search up - makes it act strange by pulling every = record=20 >>for anything in [txtKeyword]. >> >>Maybe I shouldn't have a zero for no end date. Should it be blank? = Thanks. >> >>Justin Carroll > > >------------------------------------------------------------- >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 >Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- 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 Web Archive of this list is at: http://webdna.smithmicro.com/ Justin Carroll

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:

Date Sorting (1997) Follow-Up to: Removing [showif] makes a big difference in speed (1997) Re[2]: WebCatalog on Linux (2000) [ShowIf] and empty fields (1997) Forum - Test Request (2005) Error: could not create email file in EMailFolder. Folder may (2003) WebCat2.0 acgi vs plugin (1997) Keep away (1997) Showif for mulitple variations (1997) Execute Applescript (1997) Setting up the server (1997) [cart] not being interpreted inside [founditems] (1997) Bad Cookie / Internet Option / Internet Explorer (2004) Search logic? (1998) OK, here goes... (1997) [append] and SSL (1997) Simple way to create unique SKU (1997) Questions To Answer (1997) CommandSecurity? (1997) [WebDNA] Help with ReplaceFoundItems (2009)