Hi,
I am creating a small three-tier application, using an Access database as a
back-end. Should I use DataSets and (DataRows or Bound Ojects). Which is
the best to use?

Thanks
Christo

Christo,

With an Access database I would not build a three-tier application.

When you use the standardtools from ADONET to do the job it should be in my
opinion enough.

Here is the link for a start page for that.
http://support.microsoft.com/default...b;en-us;313590

In that you find as well a link the AdoNet newsgroup where is in a
discussionthread about n-tier development now where in this book is adviced
for that.

http://www.lhotka.net/

microsoft.public.dotnet.framework.adonet

Just my thought and maybe some help?

Cor

I thought if I used a middle tier it would force me to build a few custom
classes and get away from the way I used to use VB6. The database is small
and does not really justify a sql database. I find it somewhat difficult to
get away from VB6 to .NET since I have no expierience with OOP. I have a
few text books on OOP and thought it best to get a clear understanding of
how OOP works right from the start.
..NET is so vast it difficult to decide where to start.

I will check out the links

Thanks
Christo

"Cor Ligthert" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Christo,
>
> With an Access database I would not build a three-tier application.
>
> When you use the standardtools from ADONET to do the job it should be in
> my opinion enough.
>
> Here is the link for a start page for that.
> http://support.microsoft.com/default...b;en-us;313590
>
> In that you find as well a link the AdoNet newsgroup where is in a
> discussionthread about n-tier development now where in this book is
> adviced for that.
>
> http://www.lhotka.net/
>
> microsoft.public.dotnet.framework.adonet
>
> Just my thought and maybe some help?
>
> Cor
>
>

Christo,

Making data classes is not OOP, it is a part of it when you start with VBNet
you can only use OOP. So there is no need to force it. Although you will
probably often try to use at the beginning much inline code, will you see
that you make soon more and more classes to help you and more and more
inherited controls to make life easier.

I hope this gives an idea.

Cor

It is more less like this? You create a custom control which can inherit
properties and methods from an existing class. You create your own
properties and methods (procedures, functions) which is then hidden and you
or any programmer can use this control in their applications.


"Cor Ligthert" <(E-Mail Removed)> wrote in message
news:uo%(E-Mail Removed)...
> Christo,
>
> Making data classes is not OOP, it is a part of it when you start with
> VBNet you can only use OOP. So there is no need to force it. Although you
> will probably often try to use at the beginning much inline code, will you
> see that you make soon more and more classes to help you and more and more
> inherited controls to make life easier.
>
> I hope this gives an idea.
>
> Cor
>