Data Abstraction Layer SQL/Foxpro

[DKode]

Hello,

I am creating a data layer that will handle SQL(SQLClient) and Visual
Foxpro (OleDb). The way I am thinking about creating it is create a
base class that handles setting of connectionstring and accessors for
IDbAdapter, IDbCommand, IDbConnection etc..

then in the derived classes I handle casting the connection/commands to
the proper type and return results.

I was browsing through microsofts examples on their data layer, which
is one class that uses an enum to determine the proper casting type and
returns values.

Is there any benefit to doing it the way microsoft has on their
patterns and practices site?

I would imagine that my method would be more extensible since
functionality is seperated into different derived classes.

thanks!

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

Take a look at the abstract factory pattern :
http://en.wikipedia.org/wiki/Abstract_factory

 

[DKode]

I just got done reading a book on design patterns, and reviewed the
factory pattern briefly.

I must admit, I am still having a hard time determining when to use
certain patterns and where. That article helps.

Thank you!

Sean