Kbase P14535: Browse Column attributes show different behavior after upgra
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/03/2003 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
FACT(s) (Environment):
Progress 9.1D
SYMPTOM(s):
Browse Column attributes show different behavior after upgrading to 9.1D
COLUMN:TABLE attribute shows different behavior in 9.1C and 9.1D
Using a dynamic column in a browse
Column:TABLE attribute returns Unknown ('?') in 9.1C, but returns the actual table name in 9.1D
CAUSE:
bug# 20001113-002
CAUSE:
A browse column has a number of read-only attributes, among which TABLE and DBNAME. Prior to 9.1D, these attributes were not set for dynamic columns when they were created.
In 9.1D these attributes are set when the column is created.
Because of this change in behavior, it is possible that an application behaves differently or even fails to run when using 9.1D. This has been known to occur when code to retrieve the attributes elsewhere, implemented as a workaround for the pre-9.1D behavior, started causing errors after upgrading to 9.1D.
FIX:
Use the PROVERSION function to make sure the code that fails under 9.1D but works fine on older versions is not executed on 9.1D.
If needed, code a new version of the logic that works on 9.1D and ensure this is run instead of the old code, again using the PROVERSION function.