Re: [WebDNA] Variable mystery

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 102647
interpreted = N
texte = Kenneth Grome wrote: > The interpret should not be required when that code is > inside a search context. It shouldn't? The problem definitely went away when I added that interpet context and I didn't make any other changes at that point. > What are your incoming formvariable names? I don't remember how many functions I had added to the page at that time but there certainly were: phrase mode (with three possible values: wa, wo and ws) findin (two possible values: title and all) There probably was: srscript (several possible values) There might have been: no (numeric values only) but I think I added that one later. Apart from the limited use of the phrase variable, none of these ar used in any of the scripts that caused problems, they all belong to a different search script on the page. 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)
Kenneth Grome wrote: > The interpret should not be required when that code is > inside a search context. It shouldn't? The problem definitely went away when I added that interpet context and I didn't make any other changes at that point. > What are your incoming formvariable names? I don't remember how many functions I had added to the page at that time but there certainly were: phrase mode (with three possible values: wa, wo and ws) findin (two possible values: title and all) There probably was: srscript (several possible values) There might have been: no (numeric values only) but I think I added that one later. Apart from the limited use of the phrase variable, none of these ar used in any of the scripts that caused problems, they all belong to a different search script on the page. 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:

Freeze (2003) [append] vs. [appendfile] delta + question? (1997) [protect] on NT? (1997) Why is this not false? (2001) Searching multiple Databases (1997) Webdna is dead! (2003) Can't use old cart file (was One more try) (1997) required fields (1999) [WebDNA] [thisurlplusget] and the correct use of (2013) Encrypt Users.db problem (1998) Download (1999) Setting up WebCatalog with Retail Pro data (1996) International Orders (1998) [OT] was SQL Query Question (2001) Location of Webcat site in folder hierarchy (1997) Heads up, cookies *may* be outlawed in Europe (2001) syntax question, not in online refernce (1997) [carts] and databases (1997) Before I Can Begin . . . (1998) tabs as delimiters (2004)