Re: LOOP and IF statements

This WebDNA talk-list message is from

1997

It keeps the original formatting. numero = 13573
interpreted = N
texte = >and does indeed do the showif, but I have the duplicated options>problem I described above.Use the summary parameter to show only one of each item ...>I'd like to be able to keep a database of rights/preferences for our>web-enabled clients ...Create a database of clients with all the fields you need, and onerecord per client. Then write your own WebDNA that does the samething as the [protect] tag - but works with your new clients.dbinstead of the users.db. Make sure the WebDNA you use checks for theproper username/password and also the start/end dates you'reauthorizing for that client. This lets the client change anythinghe/she needs to change in his/her database record while keeping thatdata secure from other users.You can actually store the person's credit card number very securelyif you break it up into 4 parts - and store the 4 parts in 4 separatedatabases. If you use this technique, do NOT display all parts of thecredit card number on a single template, and make sure to use 4separate forms whenever creating or changing the credit card data inthese databases - do NOT allow the client to enter all 4 parts on thesame form, and do NOT use variables to pass these values around toany other templates.Sincerely, Ken GromeWebDNA Solutionshttp://www.hui.net/dna/webdna.html Associated Messages, from the most recent to the oldest:

Re: LOOP and IF statements (Kenneth Grome 1997) Re: LOOP and IF statements (Grant Hulbert 1997) Re: LOOP and IF statements (Kenneth Grome 1997) LOOP and IF statements (Dan Keldsen 1997)

>and does indeed do the showif, but I have the duplicated options>problem I described above.Use the summary parameter to show only one of each item ...>I'd like to be able to keep a database of rights/preferences for our>web-enabled clients ...Create a database of clients with all the fields you need, and onerecord per client. Then write your own WebDNA that does the samething as the [protect] tag - but works with your new clients.dbinstead of the users.db. Make sure the WebDNA you use checks for theproper username/password and also the start/end dates you'reauthorizing for that client. This lets the client change anythinghe/she needs to change in his/her database record while keeping thatdata secure from other users.You can actually store the person's credit card number very securelyif you break it up into 4 parts - and store the 4 parts in 4 separatedatabases. If you use this technique, do NOT display all parts of thecredit card number on a single template, and make sure to use 4separate forms whenever creating or changing the credit card data inthese databases - do NOT allow the client to enter all 4 parts on thesame form, and do NOT use variables to pass these values around toany other templates.Sincerely, Ken GromeWebDNA 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:

Replace context problem ... (1997) WC2b12: Yes, Formulas.db is for real (1997) Location of Browser Info.txt file (1997) Error Lob.db records error message not name (1997) Username for Admin Group (1997) Exclamation point (1997) 2nd WebCatalog2 Feature Request (1996) Emailer Set Up (1997) Separate SSL Server (1997) multi-paragraph fields (1997) Frames and WebCat (1997) syntax question, not in online refernce (1997) Single Link browsing (1997) Nested tags count question (1997) Some Questions (1997) WebCatalog 4.0.1b1 is now available (2000) Does [Sendmail] create html? (2002) List Archives (2000) Deleting Orders (1997) no global [username] or [password] displayed ... (1997)