Re: Problem with new formvariables
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 31149
interpreted = N
texte = >I missed the release of the beta by at least of week, so I do not know if >this has beed debated here. > >It seems that the new WC does not want to import the formvariables naturally >as it used to do before. If there are archives to this list, you'll learn a lot from reviewing the last few days archive messages. This problem has been reported and debated by many of us, and we're still waiting to hear SM's decision ...Grant says he's willing to leave the variable hierarchy the way it is in 3.x -- provided he (or we) can come up with a suitable concept for a new type of variable that does NOT get overridden by formvariables. Several suggestions have been proposed, so here's another one:For page variables that cannot be overridden by formvariables, use [stext] and [smath] when creating them. The 's' signifying 'secure' which means they cannot be overridden by formvariables ... ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================############################################################# This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
Associated Messages, from the most recent to the oldest:
>I missed the release of the beta by at least of week, so I do not know if >this has beed debated here. > >It seems that the new WC does not want to import the formvariables naturally >as it used to do before. If there are archives to this list, you'll learn a lot from reviewing the last few days archive messages. This problem has been reported and debated by many of us, and we're still waiting to hear SM's decision ...Grant says he's willing to leave the variable hierarchy the way it is in 3.x -- provided he (or we) can come up with a suitable concept for a new type of variable that does NOT get overridden by formvariables. Several suggestions have been proposed, so here's another one:For page variables that cannot be overridden by formvariables, use [stext] and [smath] when creating them. The 's' signifying 'secure' which means they cannot be overridden by formvariables ... ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================############################################################# This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
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:
Shopping cart now bad (1997)
Webcatalog quitting (1997)
[subtotal] and others (1997)
Snake Bites (1997)
Professional WebDNA Hosting Solutions (2005)
RE: IIS4b2 and WebCatalog b19 (1997)
Trouble with formula.db (1997)
[WriteFile] problems (1997)
Nested vs conditional (1997)
Only charge card when product shipped ? (1997)
acrobat -> wc (1998)
[HIDEIF] inside [FOUNDITEM] (1997)
_ in front of field name (1998)
Whats wrong with this code? (1998)
URGENT! ACGI Stopped!!!! (1997)
Concealing WebCatalog in the URL (2000)
$Replace with [founditems] (1997)
Feature requests (1998)
Universal root for WC errors? (1997)
Scope of variables in multi include files (2000)