Let me jump in here as ask some further questions about this code/option functionality. I attempted to use the table structure in the code you supplied on Feb 9, in this thread, but my products have at least two options. This doesn't seem to be a problem for Crispin, but I can't figure it out. It seems to me that if the options for a product are going to be identified by an optionID and two are needed, then those options would need to be identified in their own way (as opposed to have 2 different optionIDs for a productID - or is this what you are suggesting?). What I had done instead of naming the tables that carry the options "options", I had named them size and color and those IDs are included in the products table, along with price and weight. Will the way I have my product table work or do I need to add 2 optionIDs to a product?
As for price, if the productID (not to size/color level) was equivalent to $0, then the productOptionID could be equivelant to the actual price of the product at a size color level, right? I wouldn't have to say that the smallest size of a product is $10 and that a productOption of a larger size was that price plus $5, would I? (I wouldn't know how to do that anyway)
I appreciate your publishing this code, but could I ask you to supply the code and details for products that have more than one option?
Please include as many details in the code that will be needed, including table structure, parameters and PHP code ( as I don't know PHP - I bought eCart to use with CF and MySQL, only to find out these are not supported).
I sure wish this functionality was included in the Add to Cart wizard.
I hope you can help, otherwise, how am I going to be able to move forward with using eCart, not being php trained?