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:
>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:
Extended [ConvertChars] (1997)
WebCat b13 CGI -shownext- (1997)
Look out kiwis! (2003)
[HIDEIF] inside [FOUNDITEM] (1997)
Great product and great job ! (1997)
Errata: WCS Newbie question (1997)
WebCat2b13MacPlugIn - More limits on [include] (1997)
[TCPConnect] questions/problems (2001)
changing prices in cart (1997)
[AppendFile] problem (WebCat2b13 Mac .acgi) (1997)
Help needed! (SIMS recommendation) (1998)
Help!!!! (1997)
View order not right (1997)
Looking for host (1999)
Sort Order on a page search (1997)
Generating Report Totals (1997)
Include a big block of text (1997)
[WebDNA] snow (2009)
Post Limits (1998)
View Source from cache (1997)