Re: how to check for no value while using [URL] to prevent cr
This WebDNA talk-list message is from
1999
It keeps the original formatting.
numero = 25518
interpreted = N
texte = >The only time that WebCatalog will return the field name instead of the contents >is if the field has never been used before. The best way to fix this is to >pre-assign a value to that field. Like so (with WebCat 3.x only): > >[Text]Subscriber=Friend[/Text] >. >[!] some time later [/!] >[Subscriber]!Friend]][Subscriber][/ShowIf]> >. >[!] next page [!] >Dear [Subscriber], Blah, blah, blah > >By preassigning a value, you will ensure that any test can be forced to succeed >or fail at will.Another valuable technique that uses something similar to John's concept, but is more universally useful in my opinion, is to assign all the text variables named in your form to blank values, before the form begins, like this:[Text multi=t]subscriber=&name=&address=&city=&state=&zip=[/Text]Because this will set all the form fields to blank values the *first* time the visitor visits your form page. Then use this very simple technique in your form:See how you do NOT have to use any showif's or hideif's here? This simplifies things quite a bit, don't you think?This technique will set all your form fields to blank values when no formvariables with the same names are passed into the page, and of course this is usually the situation when the visitor first visits your form page.Then when formvariables with the same names *are* passed into the page, such as when the form is revisited a second time so corrections can be made, or when the form is used to do a [replace] in a database -- the formvariables or database field values will override the blank text variable values, thus populating your form with the values you want it to have, instead of blank values!This technique greatly simplifies all your forms!If you use it all the time, you need no longer worry about having the wrong values in your forms -- unless you're inside an orderfile context of course. There are all kinds of disconcerting work-arounds required when you're in an orderfile context and when you happen to use the same variable name as one of the order file's field names -- but that's a different issue entirely ... ================================ Kenneth Grome, WebDNA Consultant 808-737-6499, http://webdna.net ================================------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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
Associated Messages, from the most recent to the oldest:
>The only time that WebCatalog will return the field name instead of the contents >is if the field has never been used before. The best way to fix this is to >pre-assign a value to that field. Like so (with WebCat 3.x only): > >[text]Subscriber=Friend[/Text] >. >[!] some time later [/!] >[Subscriber]!Friend]][Subscriber][/ShowIf]> >. >[!] next page [!] >Dear [Subscriber], Blah, blah, blah > >By preassigning a value, you will ensure that any test can be forced to succeed >or fail at will.Another valuable technique that uses something similar to John's concept, but is more universally useful in my opinion, is to assign all the text variables named in your form to blank values, before the form begins, like this:[Text multi=t]subscriber=&name=&address=&city=&state=&zip=[/Text]Because this will set all the form fields to blank values the *first* time the visitor visits your form page. Then use this very simple technique in your form:See how you do NOT have to use any showif's or hideif's here? This simplifies things quite a bit, don't you think?This technique will set all your form fields to blank values when no formvariables with the same names are passed into the page, and of course this is usually the situation when the visitor first visits your form page.Then when formvariables with the same names *are* passed into the page, such as when the form is revisited a second time so corrections can be made, or when the form is used to do a [replace] in a database -- the formvariables or database field values will override the blank text variable values, thus populating your form with the values you want it to have, instead of blank values!This technique greatly simplifies all your forms!If you use it all the time, you need no longer worry about having the wrong values in your forms -- unless you're inside an orderfile context of course. There are all kinds of disconcerting work-arounds required when you're in an orderfile context and when you happen to use the same variable name as one of the order file's field names -- but that's a different issue entirely ... ================================ Kenneth Grome, WebDNA Consultant 808-737-6499, http://webdna.net ================================------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 Kenneth Grome
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...