Re: [WebDNA] db admin tool

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 101479
interpreted = N
texte = Kenneth Grome wrote: [snip] > When a db contains encrypted data you cannot edit that field > without screwing up that record or possibly trashing the > entire db. So if you use this kind of webdna tool you must > limit its editing use to only those fields that contain > non-encrypted data. > > Naturally the tool could be built to disable editing of > encrypted fields, but it cannot figure out which fields are > encrypted all by itself, so this is an important setting > the user must make in the prefs before the tool will > function properly -- just like setting the name of > the "sku" field in each db so it knows which field contains > a unique value in each record. > > Sincerely, > Ken Grome This is pure guano! ;-) I kid. However, you *can* edit encrypted data just fine.. just decrypt into a input field and encrypt going back in. Donovan -- Donovan D. Brooke PH/FAX: 1 (608) 291-2024 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958 Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] db admin tool (Kenneth Grome 2008)
  2. Re: [WebDNA] db admin tool (Donovan Brooke 2008)
  3. Re: [WebDNA] db admin tool (Patrick McCormick 2008)
  4. Re: [WebDNA] db admin tool (Patrick McCormick 2008)
  5. Re: [WebDNA] db admin tool ("William DeVaul" 2008)
  6. Re: [WebDNA] db admin tool (Kenneth Grome 2008)
  7. RE: [WebDNA] db admin tool ("Olin Lagon" 2008)
  8. RE: [WebDNA] db admin tool ("Michael A. DeLorenzo" 2008)
  9. Re: [WebDNA] db admin tool (Donovan Brooke 2008)
  10. Re: [WebDNA] db admin tool (Gary Krockover 2008)
  11. [WebDNA] db admin tool (Patrick McCormick 2008)
Kenneth Grome wrote: [snip] > When a db contains encrypted data you cannot edit that field > without screwing up that record or possibly trashing the > entire db. So if you use this kind of webdna tool you must > limit its editing use to only those fields that contain > non-encrypted data. > > Naturally the tool could be built to disable editing of > encrypted fields, but it cannot figure out which fields are > encrypted all by itself, so this is an important setting > the user must make in the prefs before the tool will > function properly -- just like setting the name of > the "sku" field in each db so it knows which field contains > a unique value in each record. > > Sincerely, > Ken Grome This is pure guano! ;-) I kid. However, you *can* edit encrypted data just fine.. just decrypt into a input field and encrypt going back in. Donovan -- Donovan D. Brooke PH/FAX: 1 (608) 291-2024 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958 Donovan Brooke

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:

Was 5.0 Pricing, now Sandbox versus Website and ruminating (2003) still having shipCost.db Problem (1997) [WebDNA] 30 Minute Cookies (2016) ReturnRaw and redirect one last question (1997) Shopping carts and reloading pages (1997) Sort of a Dilemma! (1998) quantity minimum problem (1997) japanese characters (1997) No spaces allowed in text variable names ... ? (2002) [WebDNA] parsing xml (2010) Location of Browser Info.txt file (1997) Frames and WebCat (1997) [SearchString] (1998) Line Breaks (2003) Long/Lat (2002) Re:ListFields and [name] (1997) No spaces allowed in text variable names ... ? (2002) WCS Newbie question (1997) Server replication (1998) Help! (2000)