Mike Deeks wrote:
Why should it worry me if the extended support that I never used anyway has expired.
It should worry the owner of the project; if your project is written in a dying language, the project will die along with the language. Unless you have the sources to Windows XP and VB6 (including the dependencies)
Mike Deeks wrote:
I like the language and, as the largest project is up to 140,000 lines of code, moving to another development environment is not at all easy
It IS easy - it's also a lot of work, but it ain't complex. The longer you write new code in VB6, the more you'll have to migrate.
Mike Deeks wrote:
I am not a luddite and keep up to date with technology but my grandads King Dick socket set still seems to work as well for me as it did for him when he bought it quite a few years ago
Hehe, aight - if it ain't broke, don't fix it. You got a good point there. And yes, I admit that even 16-bit apps from Win3.1 might still run on Win7, but if something goes wrong, you're (almost) on your own. You can't compare VB6-code to "pascal code", or any other "older" language; VB6 is tied to Microsoft, is proprietary (they own the language), and it will die if they do not support the language actively.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]