Re: DON'T use old cart file!
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 14243
interpreted = N
texte = >natasha wrote: >> >> Hi Ken, >> Well the idea seems obvious, as a matter of fact, when I started thinking >> about customizing, I thougth in this direction, but I had several problems: >> > >> > What you might want to consider doing instead, would be to make >> > WebCat create a special database for each of your repeat customers - >> >> I have about 2000 regular customers-does that mean that I'll have to have >> 2000 databases? I want only the customers who WANT to save the record >> to do it, and not automatically. So I'll have to have this save >>record button >> which will have to create a database identified by customers >> accountnumber and put the items there, and I have no idea how to make WC >> to create a database that is not there already. > >Actually this could just be 1 premade (atleast it will exist even empty) >database that would store that >info by clients account number and sku they purchase, then when they return it >just looks them up via their account number that is of course different for >each client. So each time they purchase something it would add that >information to the big database, so you would have 1 database with the >information for your 2,000 clients. (you probably could also add a Would you >like your purchases saved for future reference and if they answer yes, then >save it off, just in case its a one time purchase and they may not want it as >part of their normal little custom shoppers helper section you are >working on. > >Does that make sense? Maybe Ken can come up with a cleaner >explaination to that.You wrote a fine explanation, Nevin! There's lots of ways to do this. My approach keeps the amount of RAM needed for the databases to a minimum by keeping a separate database for each customer, thus only the databases actually in use at any one time would be open.Your idea is actually simpler to code in WebDNA, but that big database (which would actually be a combination of all my small custom databases) would have to remain open all the time ... and it could actually become far larger than the main products database for the whole store.Still, I doubt you'd see much of a difference in performance either way, since WebCat's so fast to begin with ... :)Sincerely, Ken Grome WebDNA Solutions 808-737-6499 http://www.smithmicro.com/webdnasolutions/.
Associated Messages, from the most recent to the oldest:
>natasha wrote: >> >> Hi Ken, >> Well the idea seems obvious, as a matter of fact, when I started thinking >> about customizing, I thougth in this direction, but I had several problems: >> > >> > What you might want to consider doing instead, would be to make >> > WebCat create a special database for each of your repeat customers - >> >> I have about 2000 regular customers-does that mean that I'll have to have >> 2000 databases? I want only the customers who WANT to save the record >> to do it, and not automatically. So I'll have to have this save >>record button >> which will have to create a database identified by customers >> accountnumber and put the items there, and I have no idea how to make WC >> to create a database that is not there already. > >Actually this could just be 1 premade (atleast it will exist even empty) >database that would store that >info by clients account number and sku they purchase, then when they return it >just looks them up via their account number that is of course different for >each client. So each time they purchase something it would add that >information to the big database, so you would have 1 database with the >information for your 2,000 clients. (you probably could also add a Would you >like your purchases saved for future reference and if they answer yes, then >save it off, just in case its a one time purchase and they may not want it as >part of their normal little custom shoppers helper section you are >working on. > >Does that make sense? Maybe Ken can come up with a cleaner >explaination to that.You wrote a fine explanation, Nevin! There's lots of ways to do this. My approach keeps the amount of RAM needed for the databases to a minimum by keeping a separate database for each customer, thus only the databases actually in use at any one time would be open.Your idea is actually simpler to code in WebDNA, but that big database (which would actually be a combination of all my small custom databases) would have to remain open all the time ... and it could actually become far larger than the main products database for the whole store.Still, I doubt you'd see much of a difference in performance either way, since WebCat's so fast to begin with ... :)Sincerely, Ken Grome WebDNA Solutions 808-737-6499 http://www.smithmicro.com/webdnasolutions/.
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:
Extra equals signs with IE? (More debugging questions...) (1997)
You *can!!* overwrite username/password using an HTML form. Also, experts *please* see Q at end (2000)
Special characters & [sendmail] (1998)
Summing fields (1997)
No Data Results (1997)
WebCatalog can't find database (1997)
WebDNA-Talk Digest mode broken (1997)
problem serving foreign languages text (1997)
find with exceptions (1997)
emailer setup (1997)
inside out... how much? (2004)
WebCat2 beta 11 - new prefs ... (1997)
Purchase command error problem (1997)
[showif] not working (2003)
Limiting user access to .tmpl files (1997)
Can I do this with [grep]? (2002)
orders being printed (1998)
[BoldWords] WebCat.acgib15Mac (1997)
formulas.db [feature request] (2003)
unique ascending numbers (2003)