[WebDNA] Variable mystery

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 102637
interpreted = N
texte = Here's a really weird puzzle. Can anybody explain how a variable can work in a textstring but not in a search command? I was struggling with this command: [SEARCH db=ads.db&woanKWdatarq=[PAGEKW]] It should have shown two matches but came empty and it was soon obvious that the [PAGEKW] variable was the problem. However, removing the opening and edning square brackets: SEARCH db=ads.db&woanKWdatarq=[PAGEKW] showed the text string correctly with the variable replaced with the right value. I eventually figured out what I did wrong (needed a [INTERPRET] context for the variable definition earlier on the page) so the question isn't why the search command didn't work but rather why the text string did. I mean, a variable is either defined or not defined, isn't it? I had no idea there was anything inbetween. Frank Nordberg http://www.musicaviva.com http://stores.ebay.com/Nordbergs-Music-Store?refid=store Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Variable mystery (Marc Thompson 2009)
  2. Re: [WebDNA] Variable mystery (Brian Fries 2009)
  3. Re: [WebDNA] Variable mystery (Kenneth Grome 2009)
  4. Re: [WebDNA] Variable mystery (Govinda 2009)
  5. Re: [WebDNA] Variable mystery (Brian Fries 2009)
  6. Re: [WebDNA] Variable mystery (Kenneth Grome 2009)
  7. Re: [WebDNA] Variable mystery (Frank Nordberg 2009)
  8. Re: [WebDNA] Variable mystery (Kenneth Grome 2009)
  9. Re: [WebDNA] Variable mystery (Frank Nordberg 2009)
  10. Re: [WebDNA] Variable mystery (Donovan Brooke 2009)
  11. Re: [WebDNA] Variable mystery (Govinda 2009)
  12. Re: [WebDNA] Variable mystery (Terry Wilson 2009)
  13. Re: [WebDNA] Variable mystery (Frank Nordberg 2009)
  14. Re: [WebDNA] Variable mystery (Donovan Brooke 2009)
  15. Re: [WebDNA] Variable mystery (Govinda 2009)
  16. [WebDNA] Variable mystery (Frank Nordberg 2009)
Here's a really weird puzzle. Can anybody explain how a variable can work in a textstring but not in a search command? I was struggling with this command: [SEARCH db=ads.db&woanKWdatarq=[PAGEKW]] It should have shown two matches but came empty and it was soon obvious that the [PAGEKW] variable was the problem. However, removing the opening and edning square brackets: SEARCH db=ads.db&woanKWdatarq=[PAGEKW] showed the text string correctly with the variable replaced with the right value. I eventually figured out what I did wrong (needed a [interpret] context for the variable definition earlier on the page) so the question isn't why the search command didn't work but rather why the text string did. I mean, a variable is either defined or not defined, isn't it? I had no idea there was anything inbetween. Frank Nordberg http://www.musicaviva.com http://stores.ebay.com/Nordbergs-Music-Store?refid=store Frank Nordberg

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:

[Announce] Newest Commerce Site based on WebCatalog (1997) Is there a max number of fields? (1998) [WebDNA] [announce] MacTel 6.2 Minor Fixes / New Installer (2009) Cookie setting (2003) authorizenet and netscape (2002) NT Version on IIS 4.0 (1997) Checkboxes (1997) Re:2nd WebCatalog2 Feature Request (1996) Quick ShowIf question (1997) Re:FYI: Error message (1996) WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997) input problem (1999) Preventing code execution (2003) [WebDNA] Hosting Solution (2013) Multiple Ad databases? (1997) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) Date Formats (1997) WebCat2b13MacPlugIn - syntax to convert date (1997) emailer prob (1998) WebCatReference pages partly blank/empty on Webcat 3.0.7 NT (2000)