>>I've heard a lot about business object over the past few months and am a little ignorant on their usefulness. Can someone explain (in beginner's language) what advantage business objects would have over - say - putting all the code in PRG's or classes that are separate from the "presentation layer"?
>
>That is a business object *g*. Simply put, a business object is something that contains the business logic. It is generally (and should be, IMO) separated from the UI. You should also separate it from the Data Access layer also.

I was thinking there was something about COM servers or something like that - that made it more complicated than I was wanted to get into. If I can use PRG's and be as effective, that would be great. Is using PRG's to store all the business related code slower than putting the code in the form?