business vs data access tier?

what are your thoughts when using dot net data bound controls in a web site?

Use the data access object in your aspx files and remove a tier from the multi-tiered architecture, or ignore what Microsoft has created in favor of separating your data-access from your business logic?

There are two prevailing design patterns, each with advantages and limitations.

1) Use Typed DataSets to carry information through the tiers.
2) Use Custom "Business" objects to interface between the UI and Data layers.

Additionally, the concept of "State" Objects is gaining momentum.

What I consider when choosing betwen these designs is:

What level of logic (i.e. Operations) needs to be performed to make the information meaningful and robust?

For about 80% of the cases I have dealt with, "Business" objects are the way to go for non-Service Oriented implementations. When you go with an SOA, then "State" objects start to make alot of sense as they typically have lower overhead, but provide the desired benefits.