Re: Migrating Access apps to Microsoft.NET...

Tech-Archive recommends: Fix windows errors by optimizing your registry

The controls available for forms in Access are explicitly intended to be
used with data being returned from databases. While there were some bound
controls available in VB, they weren't nearly as good, and so it took a lot
longer to develop applications using VB than Access. While the bound
controls available in .Net (which all the Express languages are) are better,
empirical experience shows that it's significantly faster to develop in
Access.

An additional benefit of Access is that it has very robust reporting
capabilities. Creating reports in .Net is a lot of work.

Hopefully others will pipe in with their experiences.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Soddy" <Soddy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5F1759F4-325D-42D7-9196-13A28E09B097@xxxxxxxxxxxxxxxx
Hello!

Thanks for the info...!! And, so I'm interested in 'hearing' opinions on
why people feel that Access makes a better front-end than .NET (and
because
I'm a Newbie, also i.e. Visual Basic/Visual C# Express, etc.)
applications...??

--
Thanks!
Soddy


"Douglas J. Steele" wrote:

I think you'll find most of us feel Access makes a better front-end than
..Net applications.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Soddy" <Soddy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:190E9CB8-2471-41C6-837D-86F37112D39F@xxxxxxxxxxxxxxxx
Hello!

Brendan... Sorry for not a more pointed question... But Nikos answered
what
I was looking for... So, thanks alot for the responses!

What is your opinion of, i.e. Visual Basic Express, etc, in this
environment?

--
Thanks!
Soddy


"Nikos Yannacopoulos" wrote:

Soddy,

If I understand your question correctly, what this says is, once you
have migrated your data to SQL server, you can move away from Access
altogether - that is, for the front end also. For the latter, you can
develop a new one using a .Net language such as VB.Net, for example.

There are merits to this (such as higher portability / no need for
full
Access or Access runtime, much better protection of your app against
the
prying eye, no more FE corruptions or need for compaction etc), but
"migrate" is really the understatement of the year here... it actually
requires you to re-make the front end from scratch, in an environment
that is quite different to Access, and more time-consuming to develop
in, with no re-usability from the existing Access app. If you really
need the advantages of .Net over Access, be prepared to invest serious
time in (a) learning a new programming tool and (b) developing!

HTH,
Nikos






.

Relevant Pages

  • Re: How Can I disable autosaving when quitting Access?
    ... The compile option is disabled, I thought you could only compile if you're ... Doug Steele, Microsoft Access MVP ... that some of the controls are unboud such as the date pickers is because ... There are a few other anomalies of the sort (iCheck ...
    (microsoft.public.access.formscoding)
  • Re: How Can I disable autosaving when quitting Access?
    ... Doug Steele, Microsoft Access MVP ... that some of the controls are unboud such as the date pickers is because ... There are a few other anomalies of the sort (iCheck ... and tChange are not defined), but I'm not going to go through and look ...
    (microsoft.public.access.formscoding)
  • Re: Delete records with only Name and Date filled in
    ... I do have a Requery in the current event of the form. ... Nowif you wanted the date and time] and the Agent Control to have the ... Doug Steele, Microsoft Access MVP ... would probably be the default value of the controls themselves. ...
    (microsoft.public.access.formscoding)
  • Re: Delete records with only Name and Date filled in
    ... Nowif you wanted the date and time] and the Agent Control to have the ... Doug Steele, Microsoft Access MVP ... would probably be the default value of the controls themselves. ...
    (microsoft.public.access.formscoding)
  • Re: How refer to a column in SQL ?
    ... Doug Steele, Microsoft Access MVP ... I could store the selected Rule components in hidden controls - which ... is what i will do if I cannot refer to specific combo box columns in SQL. ...
    (microsoft.public.access.queries)