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 looks for a field in the database named date, and it uses that value instead 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 what you're trying to do, and then you will run into the problem you're seeing now - WebCat is using the 'date' value stored in your database instead of the server's date.All you have to do is change the name of your 'date' field to something else - like SaleDate for example. Then when WebCat sees [date] in your WebDNA, it will NOT be able to find a field in your database named date, so it will use the date value from your server instead ... :)Sincerely, Ken Grome WebDNA Solutions http://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 looks for a field in the database named date, and it uses that value instead 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 what you're trying to do, and then you will run into the problem you're seeing now - WebCat is using the 'date' value stored in your database instead of the server's date.All you have to do is change the name of your 'date' field to something else - like SaleDate for example. Then when WebCat sees
[date] in your WebDNA, it will NOT be able to find a field in your database named date, so it will use the date value from your server instead ... :)Sincerely, Ken Grome WebDNA Solutions http://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:
Server slowing down. (1997)
PCS Frames-Default page is solution! (1997)
Cart problem (1999)
WebCat2 several catalogs? (1997)
WebCatalog for guestbook ? (1997)
listfiles, moving files (1998)
WebStar Secure on other machine (1997)
Using a database with a short url (2000)
WebCatalog 4.0.2b5 available (2000)
HTML encoding in URLs (1997)
FM PRO Compatibility Issue - Single Database w/o Conversions (1997)
WebCat2 - many [carts] on one template page? (1997)
db access problem after switching to SSL (2001)
WebCat2 several catalogs? (1997)
NT challenges default admin/admin password (2000)
Re[2]: Re[2]: Re[2]: OT: Amazon Patents (2000)
WebMerchant & Online CC Auths (1999)
Smith Micro - no competition (2000)
resorting found set (2005)
problems with 2 tags (1997)