Re: Data Access Layer

["Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>]

We've rolled our own ORM. Of course, at the lowest level it's using
IBM's .NET provider for the connections, but all our developers ever see
is a "BusinessObject" that has fields that correspond (usually) to the
DB columns. Of course the objects also have appropriate business methods
on them. The most important thing is that you're not using SQL in your
UI layer. You want separation between your DB/Business Layer/UI layer

For example, we might have a Customer class defined as:

[DBTable("CUSTREFPF")]
public class Customer : BusinessObject
{
   [DBField("CustNo")]
   int _ID;

   [DBField("CustName", MaxLength=30)]
   string _Name;

   ....

   public int ID
   {
     get {return _ID;}
   }

   public string Name
   {
      get {EnsureLoaded(); return _Name;}
      set {SetField("_Name", value);}
   }

   ...

   public List<Order> GetOrders()
   {
      return Order.GetByCustomer(this);
   }
}

We also support a GetByExample setup so we can do simple queries:

Customer example = new Customer();
example.State = "NY";
List<Customer> NYCustomers = Customer.GetByExample(example);