Re: Updating Prices in DB (working)

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 23574
interpreted = N
texte = I am using the code below to update my database. However, when I link to the update template, I get the following message after about a minute: The attempt to load: http://www.autokrafters.com/temporary2/update...... failed I get this message when i am trying to update about 3000 records. I had done a test with a smaller database, and did not get this message. Does the larger database cause some timing-out problems? It appears that the database HAS been updated properly, but it makes me feel uneasy about it when the result of an update command is an error message! Is there a problem with the browser timing out? If so, is there a way to keep this from happening? Here is the code I was using:[showif [numberupdated]!][showif [dbpassword]=ABCD] [search db=newcatalog.db&neupdateskudatarq=[blank]&max=[numberupdated]] [FoundItems] [Replace db=catalogtest.db&eqskudatarq=[updatesku]]price=[updateprice][/Replace] [/FoundItems] [numFound] - records were found.[/search] [COMMITDATABASE catalogtest.db] [/showif][/showif] [showif [dbpassword]!ABCD] Sorry, that password is not valid [/showif]Like I mentioned... the database appears to be apdated properly. However, the error message makes me wonder if there is still something I need in the code.ThanksMike Eberly Associated Messages, from the most recent to the oldest:

    
  1. Re: Updating Prices in DB (working) (Scott Szretter 1999)
  2. Re: Updating Prices in DB (working) (Kenneth Grome 1999)
  3. Re: Updating Prices in DB (working) (PCS Technical Support 1999)
  4. Re: Updating Prices in DB (working) (Mike Eberly 1999)
I am using the code below to update my database. However, when I link to the update template, I get the following message after about a minute: The attempt to load: http://www.autokrafters.com/temporary2/update...... failed I get this message when i am trying to update about 3000 records. I had done a test with a smaller database, and did not get this message. Does the larger database cause some timing-out problems? It appears that the database HAS been updated properly, but it makes me feel uneasy about it when the result of an update command is an error message! Is there a problem with the browser timing out? If so, is there a way to keep this from happening? Here is the code I was using:[showif [numberupdated]!][showif [dbpassword]=ABCD] [search db=newcatalog.db&neupdateskudatarq=[blank]&max=[numberupdated]] [founditems] [Replace db=catalogtest.db&eqskudatarq=[updatesku]]price=[updateprice][/Replace] [/FoundItems] [numFound] - records were found.[/search] [COMMITDATABASE catalogtest.db] [/showif][/showif] [showif [dbpassword]!ABCD] Sorry, that password is not valid [/showif]Like I mentioned... the database appears to be apdated properly. However, the error message makes me wonder if there is still something I need in the code.ThanksMike Eberly Mike Eberly

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:

WebCatalog2 Feature Feedback (1996) WebDNA Solutions ... sorry! (1997) shown next / show prev (1998) emailer error -108 (1997) add to cart within a page? (1997) [LOOKUP] (1997) strange problem listfiles and movefile (long) (2000) Creating comums (1998) Bad cookie (1998) RE: Include (1998) PCS Frames (1997) creating an email message (1998) database with 10,000+ web pages stored in it? (2000) PSC recommends what date format yr 2000??? (1997) Pgp&emailer (1997) default value from Lookup (1997) ACGI processing for .html (1997) Explorer 3.0 (1997) WebCat2b15MacPlugin - showing [math] (1997) Authenticate (1999)