Convert Access 2002 to Visual Basic 6.0 - Why?

[Pam H]

I am trying to formulate a rationale for not converting an Access 2002
database to VB 6.0/Crystal Reports. Are there people out there who can supply
some technical ammunition, either for conversion or against. Thanks.

 

[Pat Hartman \(MVP\)]

What do you hope to gain from the conversion? Are you still planning on
using a Jet backend? Do you support the application yourself? Do you know
how to write VB code? Do you have any idea how much Access does for you
behind the scenes that you will now have to code for yourself?

Keep in mind that Microsoft has abandoned VB in favor of VB.net. You should
probably search the MS web site to determine when total support for VB will
be dropped. It may be as early as 2010 since the .net stuff has been out
for a few years already. Visual studio and the .net environment is a "real"
programming environment. That means that if you're not a "real" programmer,
you probably don't want to go there. I AM a "real" programmer and I don't
want to go there!

 

[Tony Toews [MVP]]

I am trying to formulate a rationale for not converting an Access 2002
database to VB 6.0/Crystal Reports. Are there people out there who can supply
some technical ammunition, either for conversion or against.

It would take at least twice as long to do the same application in VB
6.0/Crystal reports as it would in Access. You lose bound forms,
continuous forms, sub forms and a easy to use report writer.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/