Oh, I guarantee there will be those that do so. But, many of those are
probably already contemplating dropping Oracle maintenance anyway.
Figuring, we now have it working, we modified it and don't want the hassle
of putting on upgrades and redoing our mods, etc. Sort of like all the
people who dropped maintenance on SSA and then screamed bloody murder that
SSA wasn't going to give them the upgrade needed for i6.1 and above for
free like they did to all the people who stayed current with maintenance.
Then they claimed to be a 'customer' and how bad SSA treats their
'customers'. Well, I don't know if I would count someone as a 'customer'
if they haven't written me a check in years.
Software vendors have three venues to take:
- Limit their software features to only stuff that also runs on
discontinued hardware and software. Thus upsetting the customer base who
is most financially active with them.
- Limit their software to only current hardware and software, rapidly
taking advantage of the newest features. Pleasing to the most financially
active customers but very upsetting to some who may (or may not) be
current on maintenance.
- Multi versioning - Very expensive to the vendor. Requires banks of old
machines that they can't get fixes for. If they get inspired to use (for
example) a new RPG xml op code that's not supported on V4R5 do they then
have a 7.1 version and a V4R5 version that hand does it with lots of
parsing or whatnot?
- There's a fourth venue. They could claim to offer 'support'. But no
new software comes out. No new W2's, 1099's, tax compliance,etc. But if
anything existing stops working, they'll fire up that old machine and see
if they can duplicate the problem in their office or if they can blame it
on your mods. Throw a little fine print in the contract that exempts the
vendor from any new ANZOBJCVN type situations, like saying the maintenance
doesn't cover migrations to new hardware or OS.
> From our perspective, I'd rather see vendors like this than those who
still do not support 7.1 or 6.1.