[mv] pricing nightmare

[Marty Vance <mvance@lwm.com>]

******    message to minivend-users from Marty Vance <mvance@lwm.com>     ******

My catalog is completely SQL based.  My products (art) table does not
contain a price field, as the price needs to be driven by the size
selected by the user in a form.  The art table contains fields
    artID|galleryID|ratioID|orientationID|title|artist

The art is to be sold with a frame, as a set.  The size of the frame and
what group it belongs to are what need to be used to set the price.  The
frame table contains fields
    frameID|description|groupID|history

The size table contains fields
    sizeID|width|height|ratioID

I have a price table that contains fields
    sizeID|groupID|artprice|frameprice

The catalog contains 450~ pieces of art, and 24 frames.

The docs and mail list entries about CommonAdjust etc (basically the
entire pricing section) make no sense to me.  Has anyone out there done
anything this complex using SQL?

Marty Vance
LiveWire
mvance@lwm.com
www.lwm.com

-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list