Mark,
>The following happens:
>
>In Employee.cs, the CreateDataAccessObject(string dataAccessClassName) is executed with parameter = 'dataaccessoledb' => OK
>
>
>/// <summary>
>/// Factory method that creates a data access object
>/// </summary>
>/// <returns>Reference to the data access object</returns>
>protected override mmDataAccessBase CreateDataAccessObject(string dataAccessClassName)
>{
> return new EmployeeDataAccess();
>}
>
>
>The dataAccessClassName parameter seems to be ignored and the EmployeeDataAccess is instantiated without taking into account the fact that an OleDB connection is wanted:
That's right...in order for this method to instantiate a different data access object, the CreateDataAccessObject() overload needs to be changed to look at the value of the dataAccessClassname parameter and load a different data access class.
Best Regards,
Kevin McNeish
Eight-Time .NET MVP
VFP and iOS Author, Speaker & Trainer
Oak Leaf Enterprises, Inc.
Chief Architect, MM Framework
http://www.oakleafsd.com