The two tables, while they have relational keys, are completely independent. I pick the product which is really just a print. Then I pick the size (other table) which determines the price and weight. So this are two separate recordsets. I've been writing SQL since before there was a "MySQL" so this shouldn't be a challenge to write a recordset based on the SizeID.
I pick the size from a drop-down selection. Then I want the price and weight based on that selection. It just doesn't seem like this should be considered one of those "gaps" that have to be filled in eCart. My problem isn't how to do it. I just think I must be missing something here because in my opinion this is a VERY simple store and eCart should do it. So does it do this without additional work SQL/PHP? I just keep thinking I must be brain dead on this or something because I would imagine this to be a very common need in a store. One choice from a selection list and corresponding price and weight all sent to the Cart by just using the extension. Yes or No? It must be yes and I'm missing it,lol.