Kbase 13941: Loading .w to UIB deletes code or alters browse query
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Loading .w to UIB deletes code or alters browse query
There are a number of known bugs with the 7.3 UIB where if you load in
certain .w files you may find that portions of your source have been
changed or deleted.
(NOTE: THIS KBASE ASSUMES THAT THE USER HAS *NOT* EDITED THE .W CODE
OUTSIDE THE UIB!!!!!! If the .w code has been edited in the Procedure
Editor or any other text editor, it is likely that those changes
have impacted the .w source. The UIB cannot recover when users make
changes to source that violate its analyzation algorithm. Therefore,
this kbase applies ONLY to source developed exclusively in the UIB!
See kbase 13821 ["File won't load to UIB after editing in Procedure
Editor"] for more information.)
The symptom most commonly reported is that the user loads a .w that
has been previously worked-on and discovers one or more of the
following:
o The WHERE clause in the browse query has been deleted or changed
o Certain trigger blocks are missing
o Other parts of the .w are changed
There are a few known causes for this, all of which Progress
Development knows about. These include:
(1) If a calculated field exists which contains an IF condition. This
is a known bug which is scheduled to be fixed in 7.4A.
(2) If the browse is SHARED and uses external tables. This is a
known bug which is scheduled to be fixed in 7.4A.
(3) If the browse uses the NUM-LOCKED-COLUMNS attribute in any way
whatsoever. This is a known bug which is definitely fixed in
7.3B.
Progress Software Technical Support Note # 13941