Discussion Locked

VB 6 Retirement

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Good day,

I started learning to program in C/C++, then found myself needing to
write a
lot of macros in excel, so I adopted VB 6.
Now, after recently shelling out a few hundred to get the professional
edition, I find it hard to move to .NET without reaping some sort of
ROI.

Can you please inform me at what point a program compiled in vb 6 will
not
be able to run on a windows system?

I am an accounting professional in a small company, I would really hate
to
one day realize we cannot upgrade windows or have to re-write all the
apps.

I am seriously considering returning to C++ for the stability it
provides,
but find myself struggling with the RAD/ ease-of-use nature of VB.

Please Help

5 replies

by thechas

Can't even give you a good estimate.

If you manitain an archival backup of the VB run-time files, you may be able to run VB apps for several generations of Windows past when MS stopps officially supporting it.

By the same token, MS may change a DLL is the next update that will conflict with VB6, and prevent you from running your apps.

Or, take the Cobal example, their are still programs running today that were written several decades ago.

Your best tact would be to try any Windows updates or new OS versions on a test system to verify that your apps function.
Then, your last date will be dependant on when you are forced to migrate to a new OS version that does not support your apps.

Chas

by rrv

Still all your applications written in VB6 will continue to work in windows. [Check www.microsoft.com/vbasic]. You may consider to upgrade to VB7 only when you want to use advanced features.
RV

This discussion is closed to new replies.