Re: Visual Studio .Net Versus Access
- From: "Scott M." <smar@xxxxxxxxxxxxx>
- Date: Tue, 26 Feb 2008 17:38:19 -0500
Only you can really answer the question as to whether you should switch. If
you can do what your clients want and "it ain't broke", don't fix it.
Moving to .NET has many advantages, but to get there, you'll need to
re-learn almost everything you've learned since VB .NET is not VBA and to
truly get the performance gains you would want, you'd need a solid
understanding of the .NET Framework.
I would only say that (IMHO) VBA and Access as a font-end was always
something I was leery of, even back when it was in its heyday. The
scaleability and portability baggage cost just always seemed to high a prive
to pay than creating stand-alone VB front-ends.
-Scott
"Bret" <Bret@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5BC54DDB-75A0-496D-922E-8071E40E920C@xxxxxxxxxxxxxxxx
I've been an Access Developer for many years creating SQL backend and
Access
frontend programs for many companies. My question is this: Can someone
speak to the pros and or cons of moving many of my projects to Visual
Studio
/ .Net environment. Access is such a user friendly tool as an interface
to
SQL and also for forms and reporting, my customers are satisfied but I'd
like
to know if I need to take it to this level. Obviously the primary benefit
is
moving to web environment but beyond that I'd like someone to expound on
this
subject.
I am neither for or against developing in this environment and have some
Visual Studio and .Net experience.
thanks
.
- Prev by Date: Re: VS2008 Scripting WSH / COM Projects?
- Next by Date: Re: ReportViewer problem counting rows and totals
- Previous by thread: No Vs2008 Intellisense for Xaml Attributes
- Next by thread: MaintainScrollPositionOnPostback + 2nd form tag in page = problem
- Index(es):
Relevant Pages
|
