>>>Thanks, You are right!
>>>But my boss and users ask for:
>>>If the order is Normal, display discount per item according to chooseit.Qty
>>>and also display the discounted Unitprice and subtotal.
>>>----
>>>The above are succesful done become I kick the spprice table out!!
>>>But Request if The order is Special, i.e. Click on a radio button to another
>>>value.
>>>the grid to display the 'Expression on Special Price Calculation' and
>>>the 'Special Price'. Even allow user to edit or save the new expression if
>>>possible....
>>>These make great problem as need to check if .NULL. on Outer Join!!
>>>and add if possible....
>>>

---

>>>Most problem is not change the controlsource value of column but...
>>>Check on Joining table and insert row if possible... "_"
>>>
>>>If single open spprice Table in another form and access it.
>>>Of cos, all ok as No need to join the Orders and Chooseit Tables!!
>>>

---

>>>Finally, for printing reports, I got most problem on this!!
>>>Because I test for many different join on VIEW!!
>>>sometime got nothing but sometime got 20 or more duplicate or actually rows!!
>>>of cos, time consuming!! Even I can use Select Distinct....
>>>
>>>

---

>>>Okey, I would ask: May I turn down the boss request as joining problem?!
>>>Actually, I think it will be very hard to maintain even success to do it!
>>>>~<"
>>
>>I guess that your boss doesn't care what kind of relationships you gonna employ, and whatever code you gonna use. The same about joining.
>
>^_^" My too, if program do go problem, I only care my salary do not get wrong!!
> You too?! ;]

Actually I spoke about bosses. In a case of developers, they really should care about programming.