S
Simon L. Prinsloo
Guest
Traditionally, if the code shell out of the Progress session, it shares the environment of the AVM. If that is no longer the same, migration to PASOE will introduce errors without any change to the ABL source, which is unexpected. Older source will always work on newer versions (given the possible need to use a keyword forget list), in part so enable us to keep our customers up to date with the latest technology. Now we have a situation where running a) the same source code on b) the same OS in c) the same OpenEdge version, but using a different AVM, results in different behaviour. To make it worse, the described "workaround" is not universal, but unique the the particular AVM and requires run time access to files and folders that are not regularly in the PROPATH either. If that does not constitute a bug, what does?
Continue reading...
Continue reading...