Re: Access forms or VB.NET?


There's another significant factor that we haven't talked about. How big is
this project? If it's a smallish project that can be completed by one person
in days or weeks, then I'd be inclined to say: "Yes, you're right, there's
no substitute for real-world, hand's-on experience if you want to learn a
new language. Go for it." If it's a large-scale project that's going to
involve multiple developers and/or months of development time, I might be
more inclined to advise caution! :-)

--
Brendan Reynolds
Access MVP

"bernadou" <bernadou@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:89A6DCA2-4D13-4C09-9CE3-A96F09D00830@xxxxxxxxxxxxxxxx
Ok, fair enough. I guess I'm just trying to see if someone out there can
say...
"Don't use VB.NET because it is way too...."
Or
"Use VB.NET, it will provide X long term advantage..."

You get the idea.

I think we'll be fine either way. I also think I'm leaning towards VB.NET
as my personal experience has always been that if I don't just jump in and
push myself to learn, I'll just keep using what I know well. Access/VBA
has
so far never failed to be able to do what I need, but, I'm just thinking
that
VB.NET is the future so I might as well get some strong experience now.

Does someone dissagree???

B

"Brendan Reynolds" wrote:

Ease - and speed - of development is no small thing - developer time is
expensive. I haven't had an opportunity to investigate VS.NET 2005 in any
detail yet - I'm in the midst of an ASP.NET 1.1 project and don't feel
like
trying to switch horses in mid-stream - but my impression so far is, yes,
it
is a significant improvement over VS.NET 2003, but it doesn't come close
to
Access for ease - and speed - of development for the type of app to which
Access is suited.

Of course, if you are developing a type of app for which Access is not
suited, such as a web app or a distributed app, that's a different story.

You used the term 'generally speaking', but I would say that is just what
we
should not be doing. To give a meaningful answer to this question, we
have
to talk specifically, not generally. What, specifically, do you hope to
gain
from using .NET? Without knowing what those hopes are, it isn't possible
to
say whether they are realistic or not.

--
Brendan Reynolds
Access MVP

"bernadou" <bernadou@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7FA731DB-C097-4D06-BFA7-3602A8882666@xxxxxxxxxxxxxxxx
Our office is considering some options for a new internal application.
We've
discussed several options, but, I thought I'd get some outside
perspective.

Generally speaking, if we are working with SQL Svr backends, would it
be
better to develop the client apps in Access (we have a MS site license
for
Office) or VB.NET? Are there major advantages one way or the other?

The only one I could come up with so far was the ease of development in
Access forms, but, VB.NET is supposed to be getting better and better.
I'd
be the one doing the work and I have done plenty of stuff in Access
forms,
and some recent projects in ASP.NET (VB) 2.0.

Thanks for your input!

Bernadou





.

Relevant Pages

  • Re: Access forms or VB.NET?
    ... "Brendan Reynolds" wrote: ... is a significant improvement over VS.NET 2003, ... Access for ease - and speed - of development for the type of app to ... You used the term 'generally speaking', but I would say that is just ...
    (microsoft.public.access.forms)
  • Re: Trying to catch a bad user.
    ... Scott Burke ... "Brendan Reynolds" wrote: ... any code in your app has a chance to run. ... want to be sure that the vendor was an established and reputable company. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Access forms or VB.NET?
    ... "Brendan Reynolds" wrote: ... If it's a smallish project that can be completed by one person ... if you are developing a type of app for which Access is not ... You used the term 'generally speaking', but I would say that is just what ...
    (microsoft.public.access.forms)
  • Re: Access forms or VB.NET?
    ... "Brendan Reynolds" wrote: ... if you are developing a type of app for which Access is not ... You used the term 'generally speaking', but I would say that is just what we ...
    (microsoft.public.access.forms)
  • Re: Importing .frm Files
    ... "Brendan Reynolds" wrote: ... Office apps such as Word and Excel. ... and I'm now trying to create a full-blown db app. ... "Tom Ellison" wrote: ...
    (microsoft.public.access.forms)
Quantcast