A change in the engine could certainly affect a 4gl program... it
happened to me in two ways:

1. Performance. After migration, with update statistics and all that
stuff, some programs start behaving very slow... We trace the
to a particular query then we have to use hints.

2. Handling of nulls. Same version of 4gl but upgrade of the engine:
We used to assume that for Select nulls we can use empty strings
(''), it worked but with upgraded engine things were handled
properly so code has to be fixed.

So all in all, one may suppose that a version upgrade won't break code
or performance but that is not the case.

Nowadays we *always* demand *user acceptance* in a test environment
before we release something.


J.

There are cases when you can't do that of course, if it is technically
impossible.


Richard Spitz escribis:
> malc_p@btinternet.com schrieb:
>
> What new libraries do you have do accomodate that make code re-writes
> inevitable?
>
> What about "user acceptance"? Shouldn't the user ideally not notice
> anything, except maybe improved performance?
>
> I don't know about the in-engine-Java you mentioned, but why should a
> change in the engine affect the 4GL frontends?
>
> Regards, Richard
sending to informix-list

Beware of Upgrade costs. There is a big charge to go from 7.x to 9.x
or 10.x (even if you have current maintenance), so check if IBM charges
a fee to move from 9.x to 10.x.

"caver" <dmcbryde@courts.state.va.us> wrote in message
news:1134512822.562439.150730@g44g2000cwa.googlegr oups.com...
> Beware of Upgrade costs. There is a big charge to go from 7.x to 9.x
> or 10.x (even if you have current maintenance), so check if IBM charges
> a fee to move from 9.x to 10.x.
>

It doesn't
--
Neil Truby t:01932 724027
Director m:07798 811708
Ardenta Limited e:neil.truby@ardenta.com