> Oh... and why don't we use a 1:1 reference to a separate Quantity table? > Because no matter how hard I try, I can't convince people that we shouldn't > let customers use Crystal Reports to report directly from the back-end. So > in the interest of not confusing customers too much, the denormalisation is > necessary.
Just a tip: Updateable Views solves this problem :) e.g. make a View that joins your 2-tables together in one-single-view, and voila you can let your users use Crystal Reports on that stuff instead of your own normalized tables :) But then again it would be great if OJB could have more direct support for nested attributes :) Just my 2 cents... /max -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
