>Which is precisely the problem with IT. You can open the "box" - source code - and see the equivalent of a hamster in a wheel connected with duct-tape or an electric motor, but no one ever agrees that the hamster-wheel thing is wrong before it's built.

Hmmm ... not sure which side you're arguing for Mike. Which is the hamster and which is the electric motor?

~~Bonnie




>>Hi Mark,
>>
>>No, it's not archaic ... it's the way that a lot of people use Business Objects (I'm not one of them, but that's neither here nor there <g> ... I databind my controls to DataSets/DataTables rather than to Business Objects).
>>
>>So, if you're comfortable with the Business Objects methodology, there's no reason not to extend it into .NET. There's really no right/wrong way of doing this kind of stuff.
>
>Which is precisely the problem with IT. You can open the "box" - source code - and see the equivalent of a hamster in a wheel connected with duct-tape or an electric motor, but no one ever agrees that the hamster-wheel thing is wrong before it's built.