Keep them separate.

>Just a few general architecture questions...
>
>We have a few ASP.NET systems. They are split into multiple projects per system - 1 for Biz, 1 for Data, and however many for UI (some have separate "maintenance" UI's).
>
>Is this the proper architecture? Should I be concentrating on making 1 large business layer and 1 large data access layer for all projects? Or is having a separate biz layer and data layer that inherit some common functions from a utility layer the way to go? What is everyone else doing?
>
>It's always nice to have some reassurance that you are going in the right direction... ;-)