Re: Opinion Poll Please
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 41447
interpreted = N
texte = It really depends on a lot of factors...* How consistent is the product offering, now and in the future? Is it a site like allwewilleversellissimpletshirts.com? Or is it rightnowwesellshirtsbutwemightexpandintocarscomputersandturnips.com?* Can a simple calculation be developed to cover all needs?* How much data would need to be duplicated with multiple product records for the different options?* Do color or size choices affect the price, or an inventory tracking system?For flexibility and to avoid duplicating data, you might consider:product.db - product ID, name, description, etc. option.db - product ID, option ID, option description, price, weight, etc.Search the product.db, then do a nested search on the option.db by product ID to get the various options available.- brianAt 1:34 PM 7/11/02, Kimberly D Ingram wrote: >When dealing with product databases that entail various prices based on >color and/or size, etc. do you find it most efficient to: > >a) Unique Product ID for each size >b) Calculated Price >c) Other, please explain.... > >Thanks, >Kim >-- <= Brian C. Fries, BrainScan Software http://www.brainscansoftware.com =>------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
It really depends on a lot of factors...* How consistent is the product offering, now and in the future? Is it a site like allwewilleversellissimpletshirts.com? Or is it rightnowwesellshirtsbutwemightexpandintocarscomputersandturnips.com?* Can a simple calculation be developed to cover all needs?* How much data would need to be duplicated with multiple product records for the different options?* Do color or size choices affect the price, or an inventory tracking system?For flexibility and to avoid duplicating data, you might consider:product.db - product ID, name, description, etc. option.db - product ID, option ID, option description, price, weight, etc.Search the product.db, then do a nested search on the option.db by product ID to get the various options available.- brianAt 1:34 PM 7/11/02, Kimberly D Ingram wrote: >When dealing with product databases that entail various prices based on >color and/or size, etc. do you find it most efficient to: > >a) Unique Product ID for each size >b) Calculated Price >c) Other, please explain.... > >Thanks, >Kim >-- <= Brian C. Fries, BrainScan Software http://www.brainscansoftware.com =>------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Brian Fries
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:
dbQuickView 2.0 (2005)
Problems with [Math] (1998)
WebCat2: Items xx to xx shown, etc. (1997)
[OT] Mom's gift (2006)
Dates - Search and Sorting (1999)
WebCatalog can't find database (1997)
MacAuthorize and WebMerchant (1997)
Running 2 two WebCatalog.acgi's (1996)
Help! (1999)
dynamic giffing. (2000)
& in Lookups (1997)
showif comparison begins w/ and contains (1997)
Modify Database (1998)
WebCommerce: Folder organization ? (1997)
Only charge card when product shipped ? (1997)
It gets better... posting problems + Webcat 3.0.7 available - did anyone know? (2000)
Updating Prices in Online Database (1999)
[WebDNA] Digest from talk@webdna.us (2018)
OK, here goes... (1997)
Emailer port change (1997)