best practice for an entity mapping two database tables

We have a legacy database we cannot change the database schema because many systems run on it. the database designer divided a business entity persist into two database tables. for example, Product table is (ProductId, Name, ...), ProductPhoto table is (ProductId, Photo), product's photo field is stored in another table(ProductPhoto table), both ProductId is primary key. NetTiers will generate two entity classes, two datasource classes according database two tables. but in my admin UI aspx page we hope the Photo field can be 'CRUD' with the other fields of  Product seamless. what's the best practise to do that?

 You could setup a view and allow .netTiers to generate an entity object for the combined view.  This gives you only read-only access to the data though.  But, you can always take the data from the CRUD screen and populate the necessary entities for updates or deletes.