>But Jim,
>
>Couldn't one also code to add a property if a new field was detected six months later?
>
>Cheers,
>
>Jim N

Jim,

Yes one could. The point I am making is NOT that using properties is some kind of bad idea, but that one needs to analyze the entire impact of making an imlementation decision. In some cases using properties will simplify the interface, in other it will complicate the interface.

On an extremely simple basis, you can have a business object that has 30 properties that are part of the interface or you can have one that has 2 methods. When you compare 30 with 2, which interface is simpler? This example does not even begin to approach the question of maintenance and evolution of the system later.

Often the decision that seems easiest at first is later found to present problems. That's why design in OO is an iterative process. You design, start to build, revisit the design, etc.