Re: Date search bug?

This WebDNA talk-list message is from

1998

It keeps the original formatting. numero = 17705
interpreted = N
texte = Hi everyone,While I still recommend using the date formatting suggestions I made available a few days ago, there may be some of you who really don't want to mess around with a change-over like that ... so here's some CRITICAL information that may help to make your existing date range searches work properly:The following exchange occurred between myself and Grant after I sent him some files that demonstrated the date range search bug I discovered:>>Have you or anyone tracked down the date bug with those files I sent you a>>couple days ago?>>It appears to be the comma between the dates in the range. I removed the>comma and got much better-looking results. Sorry about the delay and the>misinformation.Basically, what this means is that the HTML docs are wrong -- you should NOT use a comma to separate the two values in a date range search. Instead, you should try using a blank space (or possibly a plus sign) to separate the two date values.I still don't know whether or not the earliest date value in a date range search needs to be listed first -- or if the order makes no difference. But putting the earliest date value first has eliminated problems reported with some earlier versions of WebCatalog, so it's probably still a good idea to continue that practice, just to be on the safe side ... :)Sincerely,Ken Grome808-737-6499WebDNA Solutionsmailto:ken@webdna.nethttp://www.webdna.net Associated Messages, from the most recent to the oldest:

Re: Date search bug? (Kenneth Grome 1998)

Hi everyone,While I still recommend using the date formatting suggestions I made available a few days ago, there may be some of you who really don't want to mess around with a change-over like that ... so here's some CRITICAL information that may help to make your existing date range searches work properly:The following exchange occurred between myself and Grant after I sent him some files that demonstrated the date range search bug I discovered:>>Have you or anyone tracked down the date bug with those files I sent you a>>couple days ago?>>It appears to be the comma between the dates in the range. I removed the>comma and got much better-looking results. Sorry about the delay and the>misinformation.Basically, what this means is that the HTML docs are wrong -- you should NOT use a comma to separate the two values in a date range search. Instead, you should try using a blank space (or possibly a plus sign) to separate the two date values.I still don't know whether or not the earliest date value in a date range search needs to be listed first -- or if the order makes no difference. But putting the earliest date value first has eliminated problems reported with some earlier versions of WebCatalog, so it's probably still a good idea to continue that practice, just to be on the safe side ... :)Sincerely,Ken Grome808-737-6499WebDNA Solutionsmailto:ken@webdna.nethttp://www.webdna.net Kenneth Grome

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:

international time (1997) Setting up WebCatalog with Retail Pro data (1996) RE: New WebCatalog Version !!! (1997) Webcat not processed for CACHEd image error pages (1998) [setcookie] & [redirect] (1998) W* 4.2 / WebCat (TPro) 3.0.5b / OS 8.5.1 / BW G3 (2000) Server IP address? (1998) Make sure I understand this??? (1997) Looking for WebCat developer/contractor (2000) bannerads example idiot (1997) allow or deny based on referer.... (1997) Formatting a .txt file (1998) send people in a database an email (2001) Setting up shop (1997) [OT] (waaaay OT) (2004) foreign languages, email, webcat (1998) Q: for those who use Cookies for sessions? (2004) Ot-Ip's on OSX (2004) Image Upload and Auto Resize? (2003) can WC render sites out? (1997)