Hi Marc ---

>>Fads are fads and rules are rules and never the twain shall meet. The rules of sound relational datase design were set in the 70's and they remain unchanged. The rules of OO analysis, design, and programming were set down in the 70's and 80's and they remain unchanged.
>>
>... except that no two books on the subject share the same rules, definitions etc. Face it Jim, there is no Codd and Date when it comes to OO.
>

Booch and Rumbaugh come to mind :-) There are some variances, to be sure, but there is some common-sense involved.

>>
>>Encapsulation of data and behavior is better than separated data and behavior
>>>Methods of objects are better than UDFs as they allow the encapsulation of data with the behavior.
>
>When applicable. There is a price to pay in terms of modeling that is only paid back if reuse is guaranteed. Which in the real world (and I'm talking about the domain here) is not frequent.
>

I dunno, Marc. Seems to me not much more effort to create business/application objects and use custom methods instead of UDFs even if you never intend to reuse the code.