thanx for the suggestions Gavin and Darren
(LOL, Darren! you've been thru that nightmare yourself before with
clients, yes?)
Thankfully, the guy is a bit more realistic than most. You can't model the
real world, so don't try.
The thing only needs to collect the order. Confirmation and sales happen
via email or phone - there are just too many variables. a customer really
might want Vers3 audio hardware and Vers2 audio software because it's for
2 diff jobs, just placed within the same order. A phone call or email will
have to sort it out properly.
along the lines of
for each item in cart
display item details
query for companion products for that item
if records returned
display "here are suitable accessories"
for each companion product
display companion product details
next (companion product)
end if
next (item)
Which goes along with what Gavin was suggesting and having a rules table
with 2 joins to the products table.
Darren, I agree with you that the guy needs to get the rules down pat
otherwise it'll be a pain in the bum. That's why I think I'll drop the
exclusion idea (too hard/unnecessary), although it'll be the same process
as above but use "anti-rules" ("this cannot go with that" rules).
but you're right - keep it simple. you can make things foolproof, but you
can't make them idiot proof!
thanx again, people
cheers
barry.b
(PS: My former students would be taking me to task over getting the
terminology wrong. This is cross-selling. Upselling is talking them into a
large coke when they wanted a medium. lucky they're not on list - I'd
never live it down!)
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
