Peter,

>Looking at the trace dump on the error, I realized that I need to dig into the Mere Mortal Framework to determine the SQL statements that the framework is using to "Update" the record. So I recompiled the Mere Mortal to get the debug version DLL generated.

It's OK that you recompiled the assembly, but you don't have to. MM .NET ships with the .PDB file you need for debugging.

>1. Is this error "OleDbCommand.Prepare method requires all parameters to have an explicitly set type" related to the different data supported by Access DB and the type defined in my business entity class?

No, typically this is because the OleDB provider for Access needs a little more "help" than the SQL Server data provider. You most likely need to specify more information for your parameters such as Size and Data Type. Here are a few articles on the subject:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemDataOleDbOleDbCommandClassPrepareTopic.asp

http://msdn2.microsoft.com/en-us/library/system.data.oledb.oledbcommand.prepare.aspx

>2. Below is the dump screen shows at the time of the error. Why is the mmDataAccessOleDb.CreateInsertCommand() being called and not the "Update"?

When you save a DataSet all of the command objects are created...Insert, Update, and Delete so that any rows that may be new, updated, or deleted are saved properly.

>4. When I step through the section of the MM Developer's Guide "Recompiling MM .NET Assemblies." I noticed that there are two entries for these DLLs. Is this right?
>- Mere Mortal Framework Framework 2005.
>- Mere Mortal Framework Framework 2005.
>- Mere Mortal Framework Framework Automation 2005.
>- Mere Mortal Framework Framework Automation 2005.
>- Mere Mortal Framework Framework Interfaces 2005.
>- Mere Mortal Framework Framework Interfaces 2005.
>- Mere Mortal Framework Framework Web Forms 2005.
>- Mere Mortal Framework Framework Web Forms 2005.
>- Mere Mortal Framework Framework Window Forms 2005.
>- Mere Mortal Framework Framework Window Forms 2005.

No, and this is most likely why you can't debug. If you have recompiled all the MM .NET assemblies and have created your own strong name for each, this could be why you're seeing duplicates. As I mentioned above you don't need to recompile the MM .NET assemblies unless you have made some code change to the MM .NET source.

To back yourself out of this, probably the easiest thing to do is uninstall MM .NET (it only takes a few minutes using Add/Remove Programs), then manually delete the remaining assemblies. If Windows won't allow you to delete them, you may have to go to a DOS prompt to do so (I've seen this problem on Windows 2000 machines). Afterwards, reinstall MM .NET then go through the steps mentioned in the "Stepping through MM .NET Code in the Debugger" section and you should be good to go.

Best Regards,