Database Updates

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 13264
interpreted = N
texte = I posted a related message about this last week. The single answer I got did not quench my thirst for a better solution.I have enabled several store fronts with the WebCatalog acgi. I now want to figure out an easy means of updating the various catalog.txt database files. Most clients will be maintaining these in locally operated database files and exporting updates to me. I will then use Timbuktu to place them on the server. However, it seems that the only way I can do this is to effectively close and update EVERY database file that WebCatalog has opened via the WebCatalog admin interface. Is there not a better way to close a single database and replace it with a newer version without affecting over a dozen other database files?Also, I seem to recall some discussion that the acgi version was not taking manually entered updates. I remember one client trying to manually update the ads.db and any new items he entered did not show up. Is this a known problem? Is there something special that has to be done in order to get WebCatalog to note that a change to the RAM-based file has been made by a manually entered item? John Benn, PetsForum Group Associated Messages, from the most recent to the oldest:

    
  1. Re: Database Updates (Kenneth Grome 1997)
  2. Re: Database Updates (grichter@panavise.com (Gary Richter) 1997)
  3. Database Updates (John Benn/PetsForum Grp <76703.4256@CompuServe.COM> 1997)
  4. Re: Database Updates (Kenneth Grome 1997)
  5. Database Updates (John Benn/PetsForum Grp <76703.4256@CompuServe.COM> 1997)
I posted a related message about this last week. The single answer I got did not quench my thirst for a better solution.I have enabled several store fronts with the WebCatalog acgi. I now want to figure out an easy means of updating the various catalog.txt database files. Most clients will be maintaining these in locally operated database files and exporting updates to me. I will then use Timbuktu to place them on the server. However, it seems that the only way I can do this is to effectively close and update EVERY database file that WebCatalog has opened via the WebCatalog admin interface. Is there not a better way to close a single database and replace it with a newer version without affecting over a dozen other database files?Also, I seem to recall some discussion that the acgi version was not taking manually entered updates. I remember one client trying to manually update the ads.db and any new items he entered did not show up. Is this a known problem? Is there something special that has to be done in order to get WebCatalog to note that a change to the RAM-based file has been made by a manually entered item? John Benn, PetsForum Group John Benn/PetsForum Grp <76703.4256@CompuServe.COM>

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:

Using WebCat for product info requests (1997) creator code (1997) Budget system (2003) Help!!!! (1999) Need relative path explanation (1997) Shopping with Accounts (2003) Closing databases (2003) url question (2002) another problem (1997) [WebDNA] How do we tell what's misconfigured? Or which WebDNA 7 version to use? (2011) SiteGuard Use Question (1997) hmmm (2006) OT: Google (2002) WebCat b13 CGI -shownext- (1997) HTML editing and webcatalog (2000) Re:Encyption mail was Suggestions for Topics ... (1998) Bug or syntax error on my part? (1997) Where's Cart Created ? (1997) Internet Explorer 6 Form problems (2005) SSL and reg web* (1997)