numero = 11619
interpreted = N
texte = >> Is there a way for new records appended by WebCat 2.0 >>to generate sku numbers as well? ...>> Also, I'm rather puzzled with the way delete and replace >>commands work...These issues came up for me as well, primarily because of the different functionalities of WebCat1 and WebCat2. WebCat1 automatically created a sku number when you added a record. You have to explicitly tell WebCat2 to add a SKU number to a new record -which of course requires that you provide for a SKU number (or UniqueID) field when you create your WebCat2 database. The code I use is as follows: The delete and replace functions work similarily in WC2 as in WC1 with the exception of updating the database. In WC1, anytime you appended or replaced a record to the database WC1 would quit the application -thus closing and updating the database file on disk. The next time you open the database the changes would appear. Unlike WC1, WC2 does not automatically quit and close the database (and thus write the changes to disk). The changes ARE happening but the changes are appearing in RAM cached version of the database (and not yet in the file on disk). The changes will not be written to disk until the database has been closed. To explicitly tell WC2 to close the database issue a command similar to: [CLOSEDATABASE catalog.txt] You may then open the database up in aome editor and see your changes.p.s. I should have prefaced this note with the disclaimer that this is the way I BELIEVE all this works (and all these functions are working on my site) but I hereby retain the right to wrong and I hope Grant will correct this if I'm giving out bad info.p.p.s. Perhaps the instructions for converting from WC1 to WC2 should go into a little more explanation of these differences. I, for one have been a little concerned about making sure that I issue a [closedatabase xxx] command everywhere needed to insure that I don't lose changes in the event of a crash prior to my DBs being closed...-marty ____________________________________ | Marty Schmid | | -Artwerks- | | Design/Advertising/Web Publishing | | | | T. 619.274.5029 | | F. 619.274.5656 | | e-mail: marty@artwerks.com | |____________________________________|
Associated Messages, from the most recent to the oldest:
>> Is there a way for new records appended by WebCat 2.0 >>to generate sku numbers as well? ...>> Also, I'm rather puzzled with the way delete and replace >>commands work...These issues came up for me as well, primarily because of the different functionalities of WebCat1 and WebCat2. WebCat1 automatically created a sku number when you added a record. You have to explicitly tell WebCat2 to add a SKU number to a new record -which of course requires that you provide for a SKU number (or UniqueID) field when you create your WebCat2 database. The code I use is as follows: The delete and replace functions work similarily in WC2 as in WC1 with the exception of updating the database. In WC1, anytime you appended or replaced a record to the database WC1 would quit the application -thus closing and updating the database file on disk. The next time you open the database the changes would appear. Unlike WC1, WC2 does not automatically quit and close the database (and thus write the changes to disk). The changes ARE happening but the changes are appearing in RAM cached version of the database (and not yet in the file on disk). The changes will not be written to disk until the database has been closed. To explicitly tell WC2 to close the database issue a command similar to: [CLOSEDATABASE catalog.txt] You may then open the database up in aome editor and see your changes.p.s. I should have prefaced this note with the disclaimer that this is the way I BELIEVE all this works (and all these functions are working on my site) but I hereby retain the right to wrong and I hope Grant will correct this if I'm giving out bad info.p.p.s. Perhaps the instructions for converting from WC1 to WC2 should go into a little more explanation of these differences. I, for one have been a little concerned about making sure that I issue a [closedatabase xxx] command everywhere needed to insure that I don't lose changes in the event of a crash prior to my DBs being closed...-marty ____________________________________ | Marty Schmid | | -Artwerks- | | Design/Advertising/Web Publishing | | | | T. 619.274.5029 | | F. 619.274.5656 | | e-mail: marty@artwerks.com | |____________________________________|
Marty Schmid
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...