Larry,

>Right, which is what I've done in the meantime, however that means I now have two different objects instead of one with multiple save/update methods. The stored procedures aren't the concern, it's how do I create multiple save methods (different number of parameters) in one generated object.

The best way to handle this is to have a single business object use multiple data access objects. mmBusinessObject has some built-in functionality to handle this, but it assumes one data access class per database key.

You can override your business object's GetDataAccessObject() method something like this:

public override mmDataAccessBase GetDataAccessObject(string databaseKey)
{
	if (SomeCondition)
	{
		return this.DataAccessObject;
	}
	else
	{
		return this.DataAccessObject1;
	}
}

The DataAccessObject property already exists on your business object and returns a data access class of a specfic type. You can create another property (e.g. DataAccessObject1) that also has lazy instantiation (see the code in DataAccessObject for details). In your override of GetDataAccessObject() you can check some condition to see which data access object to return.

Best Regards,