Re: UPDATE PROBLEM

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 15586
interpreted = N
texte = >> Do you have a field named Username and another one named Password >> in that database?>YES. That's the problem!Whenever you have both a Username and a Password field in your database, WebCat's built-in record-level security features are invoked. This automatic protection feature makes it impossible to replace or delete a record in the database unless you pass the proper Username and Password values along with your replace or delete command.Therefore, before you decide to use these field names in your database, it's a good idea to decide whether or not you are really going to want to enter the username and password every time you want to change or delete a record in that database. If you don't want to deal with it, simply change your field names ... :) Associated Messages, from the most recent to the oldest:

    
  1. Re: update problems ( Kenneth Grome 2004)
  2. update problems ( Terry Wilson 2004)
  3. update problem (natasha 1998)
  4. more on the Shipcost update problem (Jim Lanford 1997)
  5. Shipcost update problem (Jim Lanford 1997)
  6. Re: UPDATE PROBLEM (natasha 1997)
  7. Re: UPDATE PROBLEM (Kenneth Grome 1997)
  8. Re: UPDATE PROBLEM (natasha 1997)
  9. Re: UPDATE PROBLEM (Kenneth Grome 1997)
  10. Re: UPDATE PROBLEM (natasha 1997)
  11. Re: UPDATE PROBLEM (natasha 1997)
  12. Re: UPDATE PROBLEM (Ray Hatch 1997)
  13. Re: UPDATE PROBLEM (grichter@panavise.com (Gary Richter) 1997)
  14. Re: UPDATE PROBLEM (natasha 1997)
  15. Re: UPDATE PROBLEM (Ray Hatch 1997)
  16. Re: UPDATE PROBLEM (Ray Hatch 1997)
  17. Re: UPDATE PROBLEM (Ray Hatch 1997)
  18. Re: UPDATE PROBLEM (grichter@panavise.com (Gary Richter) 1997)
  19. UPDATE PROBLEM (natasha 1997)
>> Do you have a field named Username and another one named Password >> in that database?>YES. That's the problem!Whenever you have both a Username and a Password field in your database, WebCat's built-in record-level security features are invoked. This automatic protection feature makes it impossible to replace or delete a record in the database unless you pass the proper Username and Password values along with your replace or delete command.Therefore, before you decide to use these field names in your database, it's a good idea to decide whether or not you are really going to want to enter the username and password every time you want to change or delete a record in that database. If you don't want to deal with it, simply change your field names ... :) 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:

Dummy Credit Card Number for debug? (1997) [WebDNA] SiteBuilder Help (2008) typhoon... (1997) ups quickcost [repost] (1999) Not accepting Zero (2000) Store Example to Use (1998) Small problem (2001) Weird Syntax (2002) WebCat2 beta FTP site (1997) Date problems (1997) pop up menu's (1998) Help name our technology! (1997) [WebDNA] Good advise on [Showif] or alternative... (2012) Protect and Serve (1999) insecuretextvars preference doesn't work (2000) re: Large databases in WebCat (1997) Summ (1998) OT: RAID Options (2004) [showif]/[hideif] question (1997) PIXO (1997)