Convert Access 2003 to VB

[Guest]

Hi-

Can anyone comment on the feasability of converting Access frontends to full
VB? Has anyone done this or is it done? What functionality is lost
(assuming I'm not using JET), and are there any tools which do this? Would I
need to re-write the entire thing in VB from scratch?

Thanks,

-David

 

[Tony Toews]

Can anyone comment on the feasability of converting Access frontends to full
VB? Has anyone done this or is it done? What functionality is lost
(assuming I'm not using JET), and are there any tools which do this? Would I
need to re-write the entire thing in VB from scratch?

It's pretty ugly, a lot of work and you're significantly less
productive writing a database app in VB. So my question is why would
you want to do this?

Convert Access to Visual Basic, Delphi, Java, ASP or ASP.NET
http://www.granite.ab.ca/access/accesstovb.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Guest]

Well, basically my boss asked me if it was possible and what the difficulty
level to do so was. Hence, having no idea I asked Thanks for the info.

-David

 

[Guest]

I might add I take it its completely not advised?

 

[Larry Linson]

I might add I take it its completely not advised?

You'll find a presentation on this subject (that I did for my user group a
few years ago) at http://appdevissues.tripod.com/downloads.htm. All the
points still apply to Access versus "classic VB" (that is, VB 6 or earlier).
I haven't done a similar comparision with VB.NET but my impression is that
Windows apps are more difficult with VB.NET than with classic VB, but that
web apps are more difficult with classic VB than with VB.NET.

Unless your application fits one of the few "exceptional cases" I describe,
no, you would expend time, effort, and cost and gain nothing by converting
to VB.

Larry Linson
Microsoft Access MVP

 

[Tony Toews]

I might add I take it its completely not advised?

I can't think of any reason why you would want to convert Access to
any other development platform.

With the single exception being when an app has wildly outgrown it's
original estimates and has hundreds and hundreds of users and a number
of full time developers assigned to that app. Then you might want t

Especially if there is a large potential base of web browser users.
But even then converting the backend to SQL Server and writing just
the functionality those users require as a web app would likely be
sufficient. Those users would likely only need 10% or 20% of the apps
functionality anyhow.

Other than IT departments buying in to the high priced consultants
vision thing. All that brain washing stuff when the IT manager is a
PHB (Dilbert's Pointy Haired Boss.)

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm