Database Layer With Different Types Database

[Qingdong Z.]

I know this is a silly question, but I am looking for the best way.

I build a windows application with standard version and enterprise version.
Standard version use local SQL/Access as database. Enterprise version use
Centralized Web Service as Database. Which is the easiest way to handle this?
I have too many classes have data access.

I can create following classes, How could I use Interface or other ways to
call right DB?
class1
class1_db_sql
class1_db_acces s
class1_db_webse rvice

[Daniel]

Bit weird to use multiple db formats but anyway...

I'd make an interface class then inherit from that and override dependant on
which db.

so say interface was called MyInterface

public class dbAccess : MyInterface //inherit interface

public class dbEnterprise : MyInterface //inherit interface
then when u wanna use the access one:

MyInterface m = new dbAccess();

or the enterprise one

MyInterface m = new dbEnterprise();

And that ofcourse can neatly be used with the factory pattern.

then ur code for your method calls for both enterprise and access versions
will not change.
"Qingdong Z." <Qi*******@disc ussions.microso ft.comwrote in message
news:83******** *************** ***********@mic rosoft.com...

>I know this is a silly question, but I am looking for the best way.

I build a windows application with standard version and enterprise
version.
Standard version use local SQL/Access as database. Enterprise version use
Centralized Web Service as Database. Which is the easiest way to handle
this?
I have too many classes have data access.

I can create following classes, How could I use Interface or other ways to
call right DB?
class1
class1_db_sql
class1_db_acces s
class1_db_webse rvice

[sloan]

Go the the result of this search
http://groups.google.com/groups/sear...ccess+Layer%22

I answered the question more detailed there.


"Qingdong Z." <Qi*******@disc ussions.microso ft.comwrote in message
news:83******** *************** ***********@mic rosoft.com...

I know this is a silly question, but I am looking for the best way.

I build a windows application with standard version and enterprise

version.

Standard version use local SQL/Access as database. Enterprise version use
Centralized Web Service as Database. Which is the easiest way to handle

this?

I have too many classes have data access.

I can create following classes, How could I use Interface or other ways to
call right DB?
class1
class1_db_sql
class1_db_acces s
class1_db_webse rvice

[Dave Sexton]

Hi,

It sounds to me like you need a way of easily switching the data layer at compile-time, not runtime. In that case you can extend
Daniel's idea and add conditional compilation to choose the appropriate database at compile-time:

#define ENTERPRISE

using System;

static class DALFactory
{
static IDataAccessLaye r Create()
{
#if ENTERPRISE
return new EnterpriseDAL() ;
#else
return new StandardDAL();
#endif
}
}

If you're using VS.NET then it's even easier. Don't use the #define directive, but instead create a new configuration for your
solution in the Configuration Manager, and define the symbols there. When you want to build for the enterprise select the new
ENTERPRISE configuration that you created from the dropdown (instead of RELEASE or DEBUG). If you want a standard build, just
choose RELEASE.

HTH

--
Dave Sexton

"Qingdong Z." <Qi*******@disc ussions.microso ft.comwrote in message news:83******** *************** ***********@mic rosoft.com...

>I know this is a silly question, but I am looking for the best way.

I build a windows application with standard version and enterprise version.
Standard version use local SQL/Access as database. Enterprise version use
Centralized Web Service as Database. Which is the easiest way to handle this?
I have too many classes have data access.

I can create following classes, How could I use Interface or other ways to
call right DB?
class1
class1_db_sql
class1_db_acces s
class1_db_webse rvice