First, its important to understand tiered development.
This will make more simple for you.
Check this:
http://sholliday.spaces.live.com/?_c...26ayear%3d2006
As the previous poster pointed out............ ...Check into the Enterprise
Library data access application block. (I'll abbreviate this as ELDAB for
this post)
One aspect of the ELDAB is that it allows a "common syntax" to whichever
database you're talking.
Access
Excel
Sql Server
Oracle
And you're able to switch the database....... ..in a dataConfigurati on.config
file (1.1, 2.0 is the same concept but a little different)
............
Back to the tiers:
If you're datalayer object only returns
DataSet's
IDataReader's
Scalars
Void's/Nothing's
The the backend db doesn't become as big an issue.
.........
Now , sometimes the ELDAB is not sufficient.
The next thing you could do is create Interface(s) for the DataAccess Layer.
Lets call one
IEmployeeDataLa yerObject
pubic DataSet GetInfo(int empid)
public void UpdateInfo(int empid, string fname, string lname)
You create 2 concrete versions of IEmployeeData
EmployeeDataFor Access : IEmployeeDataLa yerObject
and
EmployeeDataFor Oracle : IEmployeeDataLa yerObject
You create a simple Factory class, which returns 1 of the 2 concrete
objects.
See
12/1/2005
Understanding the Simple Factory Pattern
http://sholliday.spaces.live.com/?_c...26ayear%3d2005
and look at the "reflection " example.
Normally, you don't have to go to the extreme of doing this last step.
However, I send alot of xml into my datalayers.
IEmployeeDataLa yerObject
public void UpdateInfo(XmlD ocument xmlDoc)
In this case, ........... I can actually send the raw xml into Sql
Server.....beca use it has an OPENXML command.
For Access, there is no internal Xml functionality, so I have .. create a
transaction in code, loop over the xml, and run several statements against
the Access database.
For Oracle, I've played with their xml functionality, and as far as 9.xxxx,
I was disappointed in it.
In this case, the ELDAB is deficient. But I can get around it with the
interfaces for the IEmployeeDataLa yerObject, several concrete classes, and
using the "Simple Factory" design pattern with reflection (or "key" method)
This should help.
But first off, you need to get the Tiers correct, or you're just
complicating your life too much.
"S. Lorétan" <tynril@[nospam]gmail.comwrote in message
news:%2******** ********@TK2MSF TNGP03.phx.gbl. ..
Hi guys,
I'm coding an application connected to a database. I have some clients
that
use this program with 2 or 3 computers, and I use MsSQL Express for them.
But if the client needs more computers to be connected to the database, I
have to use a standard MsSQL. No problem with that, but I want to be able
to
switch from a database provider to another in an easy way.
I know that this way to do is called "Data(base) abstraction layer", but I
don't know how to use it. I've read some articles around the Internet,
like
this one http://www.codeproject.com/cs/database/dalgen.asp, but I don't
want
to have to regenerate source code each time I change the database. If it
is
possible, I would like to use SQL to do my queries, and I have to be able
to
do "complex" queries (joining, subselecting, ...).
The databases I would like to be able to use are MsSQL (Express or not),
MySQL, and if possible Oracle.
Is there something to do this in the Framework? Or maybe some open source
library?
Thank you for your help.
