ASP.NET C#: Which Design Pattern should I use and why?

[acropolis]

I am developing an app in ASP.NET C# and came across the following scenario:[*]I will have to create some maintenance screens for different entities (tables)[*]Those entities will basically have the same behaviour within the UI: Search, GetById, Save, Create and GetAll[*]The entities may have different structure i.e. different properties (fields)As I am talking about 20 plus admin screens, which design pattern I could take advantage of in order to minimize the amount of code I will have to write?I though of the bridge pattern but I am a little confused on how to implement it ...A little bit of the technology background I am using:[*]ASP.NET classic (n-tier)[*]LINQ to SQL and DAO objects[*]SQL Server 2005