Thanks for your comments Carsten.
"CT" <carstent@spammersgoawaydotnetservices.biz> wrote in message
news:O8Tfqj5KFHA.3184@TK2MSFTNGP09.phx.gbl...
> Hi Doug,
>
> I guess this is one of those ofthen asked questions; why bother build the
> "correct" infrastructure if it isn't needed? Well, you describe it as a
> "small" application, so the question here is if it's more like a utility
> than won't be extended in any major way in the future? If so, I'd say go
> with the simple single layer approach,m saving time. However, if you will
be
> extending your app in the future, the second approach is probably the
best.
> Now, there are more issues you might want to consider, but I'm just trying
> to keep it simple and give you an idea of how to gte started.
>
> --
> Carsten Thomsen
> Enterprise Development with VS .NET, UML, AND MSF
>
http://www.apress.com/book/bookDisplay.html?bID=105 >
> "Doug Bell" <dug@bigpond.com> wrote in message
> news:O%23ecAg2KFHA.3356@TK2MSFTNGP12.phx.gbl...
> > Hi I am about to start to build a small windows application that will
> > periodically retrieve selected data from a Database (DB2) and update an
> > Access DB.
> >
> > My question is what is the best way to structure this VB Dot Net
project.
> >
> > Should I build all the logic into a single application layer
> > or have a main application layer that handles the scheduling and calls a
> > data layer that returns a dataset (holding the returned DB2 data) and
then
> > pass the data set to another data layer that handles the updating of the
> > Access database?
> >
> > Thanks for any advice,
> >
> > Doug
> >
> >
>
>
