When my bag of tricks was nearly empty, I wanted to add quite a few fields to the Users table and needed several new methods for creating the datasets from that table. Having trouble understanding the "Mere Mortals way", I decided to create another business object based on the User table with it's own set of select statements and procedures. I have now figured out how to do it the "Mere Mortals way", with a User biz object subclassed from mmUser. However, I am frustrated by the requirement to use SQL command strings rather than stored procedures. Other than the obvious fact that having two business objects referencing the same table creates some duplication, if I only use the new biz object for my custom purposes, is there any down side to having two biz objects referencing the same table? It looks like it basically functions in the same way it would if I built a biz object based on a SQL View. Any thoughts?