Okay, I kind of see what you mean now. I think. :D
I have seen apps built this way, where the UI reaches directly into the DAL and uses the entities from there. It's a valid approach, but in my opinion, you lose a lot of the benefits of the n-tier architecture that way.
To a lot of folks, I suppose it seems repetitive to build entities to wrap the database fields, then build business objects that in large part merely represent those entities. But part of the objective of n-tier is the isolation of layers. In other words, the UI only reaches into the BLL, the BLL only reaches into the DAL, and the DAL only reaches into the DB.
Letting the UI "jump over" the BLL into the DAL, to me, partly defeats the purpose of having a BLL in the first place.
Of course, this is only my opinion. Other folks may differ.