Well, this has opened up a can of worms. With my old method of just adding a column to the Customers table, I would just add a property to my Customer class (e.g. Customer.GetsJobsNewsletter). Now, with multiple child records in the ancillary table, I have to either use or write some kind of mapper to map the child records to Customer class properties with the proper names... Plus, when updating the Customer, I have to somehow loop through all the newsletter child records and update each one. Ugh.