Windows Application and Data Layer design

[newbie]

Hello,

If I have posted the question in the wrong group, I apologize.

I am building a windows application (in c#) that will be interacting
with an existing Access database. This database will eventually be
upgraded to SQL Server 2000. Current applications (C++Builder) that
interact with that database have the GUI and database access
tightly-coupled. This has led to many issues that are often discussed
in newsgroups.

I have read many threads that suggest creating a database or data
layer to separate database access from the GUI, and I agree with many
of the benefits this provides.

Questions or issues I have:
- Do I create a single class that contains methods for retrieving
data?
- Do I create a group of classes to retrieve data divided into
logical groups (i.e. User class, System class)

Regardless of the class structure
- Do the methods return collection of objects or do they return
datasets?

Thanks,

new2c#

[Darin]

Hi,

I would take a look at this thread:
http://www.experts-exchange.com/Prog..._20848629.html

I suggest you create a data access layer. I would design to be able to
handle multiple datasources (Access, MS SQL ...). This way you can use this
data layer in other projects and will eliminate recoding.

Good Luck
"newbie" <ms******@yahoo.com> wrote in message
news:51************************@posting.google.com ...

Hello,

If I have posted the question in the wrong group, I apologize.

I am building a windows application (in c#) that will be interacting
with an existing Access database. This database will eventually be
upgraded to SQL Server 2000. Current applications (C++Builder) that
interact with that database have the GUI and database access
tightly-coupled. This has led to many issues that are often discussed
in newsgroups.

I have read many threads that suggest creating a database or data
layer to separate database access from the GUI, and I agree with many
of the benefits this provides.

Questions or issues I have:
- Do I create a single class that contains methods for retrieving
data?
- Do I create a group of classes to retrieve data divided into
logical groups (i.e. User class, System class)

Regardless of the class structure
- Do the methods return collection of objects or do they return
datasets?

Thanks,

new2c#

[newbie]

Hey Darin,

Thank you very much. Your response was extremely helpfully. Lots to
read and learn (and try).

newbie
"Darin" <d> wrote in message news:<e5**************@tk2msftngp13.phx.gbl>...

Hi,

I would take a look at this thread:
http://www.experts-exchange.com/Prog..._20848629.html

I suggest you create a data access layer. I would design to be able to
handle multiple datasources (Access, MS SQL ...). This way you can use this
data layer in other projects and will eliminate recoding.

Good Luck
"newbie" <ms******@yahoo.com> wrote in message
news:51************************@posting.google.com ...

Hello,

If I have posted the question in the wrong group, I apologize.

I am building a windows application (in c#) that will be interacting
with an existing Access database. This database will eventually be
upgraded to SQL Server 2000. Current applications (C++Builder) that
interact with that database have the GUI and database access
tightly-coupled. This has led to many issues that are often discussed
in newsgroups.

I have read many threads that suggest creating a database or data
layer to separate database access from the GUI, and I agree with many
of the benefits this provides.

Questions or issues I have:
- Do I create a single class that contains methods for retrieving
data?
- Do I create a group of classes to retrieve data divided into
logical groups (i.e. User class, System class)

Regardless of the class structure
- Do the methods return collection of objects or do they return
datasets?

Thanks,

new2c#