Our customers have most of their apps developed in actual technologies, no problem there;
but we also know most of them still use legacy apps developed in the early 90s with vb6 and vfp9,
Now today almost all of our customers with these apps are reluctant to invest in migrating those legacy apps simply because they are very much customized for engineering and specific specialized tasks. The investment would be high as it was originally or maybe more.And those apps still work just fine and still they can virtualize the machine so they really are not moving.
Our company is today in charge of further developments and maintaining as much as possible legacy apps with these companies. We are trying to prevent and see today how far in the future these legacy apps will go....
We fear its not even enough to migrate. Maybe we are already too late.
So our proposal to our customers will be something like maintain what can be maintained for at least another decade and migrate what will stop no matter what in the next few years. but in all cases prevent a situation that can be hurtful business wise.
Here is my question, how far in the future will these vb6 and vfp9 legacy apps go ?
Since they are not the core system but yes they do perform specific important tasks can we keep them like that with some sort of environment ? and if so what environment would that be?