So I found what I think is a bug in mmBusinessObject. In the LoadRow(object pk) method there is the code that creates the SELECT statement and then a call is made to getDataSet(). But because it doesn't send a CommandType, getDataSet uses the DefaultCommandType which for me is stored procedure. That screws things up, so I'm gonna fix it.

But my question is, if I fix this and a new version of MM.Net comes out and overwrites my mmBusinessObject class, what happens?

I see from the help that I have to recompile the assemblies. Are there any other "best practices" in changing the MM classes?

Thanks,

Eric