[WebDNA] Re: Math Date issue
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102057
interpreted = N
texte = You're quite welcome! Although Gary's solution is=20 ultimately a shorter, cleaner solution. Terry THANK YOU, TERRY!!! I only subscribe to digest mode (how do I switch=20 to feed mode, by the way?), so I just saw your=20 answer. It works perfectly now! Knew it had to be=20 something stupid. I mean, not that you'd have to=20 be stupid to figure it out -- that would be=20 insulting the guy who helped me. Aww, crap. You=20 know what I meant. :-) Gary, thank you, too for your simple solution. If=20 Terry's hadn't worked, you were in the pipeline.=20 Good, brief code. ----- Patrick Junkroski =46rom:=A0Terry Wilson <
terry@terryfic.com> Date:=A0February 19, 2009 1:38:12 PM EST To:=A0<talk@webdna.us> Subject:=A0Re: [WebDNA] Math Date issue Reply-To:=A0<talk@webdna.us> should be this: &group1type=3Ddate&group2type=3Ddate Terry Hi - I'm using WebDNA Commerce Edition 6.0 on a G5 Xserve under 10.3.9. I have code that is supposed to search a database=20 and show any advertiser's status (called=20 linkexpires, in this example) falls between=20 today's date and a week from now. It generally=20 seems to work, but every once in a while I have=20 an issue like this one. Here's my code (minus some HTML to make it cleaner): The following companies have LINKS =A0whose status=20 will expire between [date] and [math=20 date]{[date]}+{00/07/0000}[/math] [search=20 db=3DTheSeniorGuide.db&linkexpirestype=3Ddate&group1field=3Dlinkexpires&grou= p2field=3Dlinkexpires&group1fieldtype=3Ddate&group2fieldtype=3Ddate&legroup1= datarq=3D[math=20 date]{[date]}+{00/07/0000}[/math]&gegroup2datarq=3D[date]&ascompanynamesort= =3D1] | Company | Address | City | State | Zip | <= th>Expiration
|---|
[founditems][hideif [linkexpires]=3D] | [companyname] | [streetaddress] | [city] | = [state] | [zip] | [linkexpires] |
[/hideif][/founditems] [/search] Here's the output: The following companies have=A0LINKS=A0whose status=20 will expire between 02/19/2009 and 02/26/2009 CompanyAddressCityStateZipExpirationProvince=20 Place of DePaul6403 Granby=20 StNorfolkVA2350502/25/2010Province Place of=20 MaryviewOne Bon Secours=20 WayPortsmouthVA2370302/25/2010 If the output didn't copy properly, it shows two listings who expire 02/25/2= 010 The day and month of the expiration is true, but=20 the year is wrong. This advertiser shouldn't show=20 up here until one year from now. Where's my coding error? Anyone? =A0Anyone? =A0Bueller? TIA ----- Patrick Junkroski -- Terry Wilson | terry@terryfic.com | http://terryfic.com http://WhosComing.com - a simplified, affordable online reservation system http://TightJacket.com -- stylish protection for your laptop -------------------------------------------------------------------------- Attitude is the only difference between ordeal and adventure.
Associated Messages, from the most recent to the oldest:
You're quite welcome! Although Gary's solution is=20 ultimately a shorter, cleaner solution. Terry THANK YOU, TERRY!!! I only subscribe to digest mode (how do I switch=20 to feed mode, by the way?), so I just saw your=20 answer. It works perfectly now! Knew it had to be=20 something stupid. I mean, not that you'd have to=20 be stupid to figure it out -- that would be=20 insulting the guy who helped me. Aww, crap. You=20 know what I meant. :-) Gary, thank you, too for your simple solution. If=20 Terry's hadn't worked, you were in the pipeline.=20 Good, brief code. ----- Patrick Junkroski =46rom:=A0Terry Wilson <terry@terryfic.com> Date:=A0February 19, 2009 1:38:12 PM EST To:=A0<talk@webdna.us> Subject:=A0Re: [WebDNA] Math Date issue Reply-To:=A0<talk@webdna.us> should be this: &group1type=3Ddate&group2type=3Ddate Terry Hi - I'm using WebDNA Commerce Edition 6.0 on a G5 Xserve under 10.3.9. I have code that is supposed to search a database=20 and show any advertiser's status (called=20 linkexpires, in this example) falls between=20 today's date and a week from now. It generally=20 seems to work, but every once in a while I have=20 an issue like this one. Here's my code (minus some HTML to make it cleaner): The following companies have LINKS =A0whose status=20 will expire between [date] and [math=20 date]{[date]}+{00/07/0000}[/math] [search=20 db=3DTheSeniorGuide.db&linkexpirestype=3Ddate&group1field=3Dlinkexpires&grou= p2field=3Dlinkexpires&group1fieldtype=3Ddate&group2fieldtype=3Ddate&legroup1= datarq=3D[math=20 date]{[date]}+{00/07/0000}[/math]&gegroup2datarq=3D[date]&ascompanynamesort= =3D1]