Re: ANother SHOWIF problem
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 13454
interpreted = N
texte = >In my database, I have divided the on sale date of an item into month>(1-12), day (1-31), and year (01-99) fields (for a number of reasons).What's the name of your on sale date field?You named it date, didn't you?That's the problem ... :)>For some reason, the following code (which is inside a [SEARCH] context)>*always* displays the on sale date.>>[SHOWIF [MATH][DATE][/MATH]<[MATH]{[MTH]/[DAY]/[YR]}[/MATH]]
On sale>[MTH]/[DAY]/[YR][/SHOWIF]You didn't mention it, but this WebDNA is also located inside a[founditems] context, isn't it? Here's what you're running into ...When WebCat sees a [date] tag inside a [founditems] context, it looksfor a field in the database named date, and it uses that valueinstead of the server date.That's why it is never a good idea to use date as a field name,because eventually you will want to do something exactly like whatyou're trying to do, and then you will run into the problem you'reseeing now - WebCat is using the 'date' value stored in your databaseinstead of the server's date.All you have to do is change the name of your 'date' field tosomething else - like SaleDate for example. Then when WebCat sees[date] in your WebDNA, it will NOT be able to find a field in yourdatabase named date, so it will use the date value from your serverinstead ... :)Sincerely, Ken GromeWebDNA Solutionshttp://www.hui.net/dna/webdna.html
Associated Messages, from the most recent to the oldest:
>In my database, I have divided the on sale date of an item into month>(1-12), day (1-31), and year (01-99) fields (for a number of reasons).What's the name of your on sale date field?You named it date, didn't you?That's the problem ... :)>For some reason, the following code (which is inside a
[search] context)>*always* displays the on sale date.>>[SHOWIF
[math][date][/MATH]<
[math]{[MTH]/[DAY]/[YR]}[/MATH]]
On sale>[MTH]/[DAY]/[YR][/SHOWIF]You didn't mention it, but this WebDNA is also located inside a
[founditems] context, isn't it? Here's what you're running into ...When WebCat sees a
[date] tag inside a
[founditems] context, it looksfor a field in the database named date, and it uses that valueinstead of the server date.That's why it is never a good idea to use date as a field name,because eventually you will want to do something exactly like whatyou're trying to do, and then you will run into the problem you'reseeing now - WebCat is using the 'date' value stored in your databaseinstead of the server's date.All you have to do is change the name of your 'date' field tosomething else - like SaleDate for example. Then when WebCat sees
[date] in your WebDNA, it will NOT be able to find a field in yourdatabase named date, so it will use the date value from your serverinstead ... :)Sincerely, Ken GromeWebDNA Solutionshttp://www.hui.net/dna/webdna.html
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:
WebCatalog and WebTen (1997)
Close Databases Crash? (1998)
Search/sort in URL Was: GuestBook example (1997)
Best way to handle 404 errors with WebDNA and Web* V (2003)
Bit off subject -- Faxing orders (1997)
Date search - yes or no (1997)
'does not contain' operator needed ... (1997)
default value from Lookup (was Grant, please help me) (1997)
Help name our technology! (1997)
WebCat2 beta 11 - new prefs ... (1997)
Limiting user access to .tmpl files (1997)
Help name our technology! (1997)
Just Testing (1997)
Fun With [TCP Connect] (1998)
Nested tags count question (1997)
Only charge card when product shipped ? (1997)
[WebDNA] sudo and shell (2010)
Error Log.db --however (1997)
A quickie question (1997)
emailer settings and control questions (1997)