Walter,

>Wouldn't the dataAccessClassName come in as String.Empty or null in this case? I'm talking about a SPELLING MISTAKE. No error is raised, it just uses the wrong provider and crashes later.
>
>> Actually, CreateDataAccessObject() is eventually in the call chain.

You're right...I changed mmBusinessObject.CreateDataAccessObject() so it calls Factory.CreateDataAccessObject() rather than resolving the concrete data access class in the business object. Also changed behavior so that unknown data access class names no longer default to returning a SQL Server data access class, but instead throw an exception.

Picture your name in the next What's New Guide--which has been proven to increase honorees sex appeal. You may want to start wearing a disguise when leaving the house.

Best Regards,