Re: RequiredFields template

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 12382
interpreted = N
texte = >I currently have the following response for checking fields > >[ShowIf [Field1]=] >Please hit the back button and fill in Field One

[/ShowIf] > >[ShowIf [Field2]=] >Please hit the back button and fill in Field Two

[/ShowIf] > >The problem is if multiple fields are left blank, the template returns a >list of Please hit the back button and fill in Field such and such >(there are about 20 fields on the page). Functional, but not necessarily >pretty > >I would prefer to have it return just one message instead. (Please hit >the back button and fill in all required fields) Any ideas on a >solution?This is something I've always wanted but I don't remember if I've ever mentioned before. I think there's a way to do this with math variables if I'm not mistaken ... Here's another approach you may want to use for *some* append situations:I've realized that even if you force people to enter data into a field, you still cannot force them to enter the 'correct' data into that field. Sometimes people think they are getting away with something by entering bogus data. Here's a way to eliminate some of those bogus database records ...Don't even try to check your forms for blank fields. Instead, let people enter whatever they want to enter ... then use some WebDNA to automatically delete any records that have been entered with 'blank' data in your 'required' fields.When I do this, I put some text next to a required field saying this field is required, but I do not try to enforce that requirement. If the person thinks he/she can get away with something by NOT entering data into one of the fields I labeled as required, I just let them think that.Then after they append their record (with blank fields) to the database ... thinking they have gotten away with something ... my WebDNA deletes that record.This makes it very easy for me to create my append forms, because I don't bother to do a lot of checking before the data gets entered, I simply delete any new records that don't live up to my requirements - after they have already been added to the database.While I realize that this will *not* be a good solution in cases where you really *need* to make people enter something, it sure works great in other situations ... :)Sincerely, Ken Grome WebDNA Solutionshttp://www.hui.net/dna/webdna.html Associated Messages, from the most recent to the oldest:

    
  1. Re: RequiredFields template (Glenn Davis 1997)
  2. Re: RequiredFields template (Trevor Crist 1997)
  3. Re: RequiredFields template (Glenn Davis 1997)
  4. RequiredFields template (Trevor Crist 1997)
  5. Re: RequiredFields template (Kenneth Grome 1997)
  6. Re: RequiredFields template (Grant Hulbert 1997)
  7. Re: RequiredFields template (Glenn Davis 1997)
  8. Re: RequiredFields template (Kenneth Grome 1997)
  9. Re: RequiredFields template (Grant Hulbert 1997)
  10. Re: RequiredFields template (Grant Hulbert 1997)
  11. Re: RequiredFields template (Kenneth Grome 1997)
>I currently have the following response for checking fields > >[ShowIf [Field1]=] >Please hit the back button and fill in Field One

[/ShowIf] > >[ShowIf [Field2]=] >Please hit the back button and fill in Field Two

[/ShowIf] > >The problem is if multiple fields are left blank, the template returns a >list of Please hit the back button and fill in Field such and such >(there are about 20 fields on the page). Functional, but not necessarily >pretty > >I would prefer to have it return just one message instead. (Please hit >the back button and fill in all required fields) Any ideas on a >solution?This is something I've always wanted but I don't remember if I've ever mentioned before. I think there's a way to do this with math variables if I'm not mistaken ... Here's another approach you may want to use for *some* append situations:I've realized that even if you force people to enter data into a field, you still cannot force them to enter the 'correct' data into that field. Sometimes people think they are getting away with something by entering bogus data. Here's a way to eliminate some of those bogus database records ...Don't even try to check your forms for blank fields. Instead, let people enter whatever they want to enter ... then use some WebDNA to automatically delete any records that have been entered with 'blank' data in your 'required' fields.When I do this, I put some text next to a required field saying this field is required, but I do not try to enforce that requirement. If the person thinks he/she can get away with something by NOT entering data into one of the fields I labeled as required, I just let them think that.Then after they append their record (with blank fields) to the database ... thinking they have gotten away with something ... my WebDNA deletes that record.This makes it very easy for me to create my append forms, because I don't bother to do a lot of checking before the data gets entered, I simply delete any new records that don't live up to my requirements - after they have already been added to the database.While I realize that this will *not* be a good solution in cases where you really *need* to make people enter something, it sure works great in other situations ... :)Sincerely, Ken Grome WebDNA Solutionshttp://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:

'page impression' techniques for banner ads (1999) Adding muliple sku + quantities (1999) RE: A zip code search (1998) creator code (1997) Bug or syntax error on my part? (1997) [object] Tag & WebDNA Support (2005) Converting a Magazine to a Web Site with WebCat (1999) Help! WebCat2 bug (1997) The address of this list has changed to WebCatalog-Beta@talk.smit (2000) Unexpected comparison behavior change in 4.5.1 (2003) [writefile] (1997) PCS Frames (1997) (1997) CommandSecurity? (1997) Server Freeze (1998) Payflow Pro help is here (2002) Locking up with WebCatalog... (1997) serial number dishing (1997) [WebDNA] PayPal Integration (2017) Allowed fields in formulas.db (1998)