Kbase 17372: Bug fixes for the ADM in Progress Version 8.2B
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Bug fixes for the ADM in Progress Version 8.2B
INTRODUCTION
============
This knowledgebase entry is a summary of ADM bug fixes made for
8.2B. The files changed by these fixes are method\tableio.i,
method\record.i, template\row-head.i, template\pnstates.i, and
method\broksmrt.i.
BUGS
====
1. Group-assign links were re-opening a query more than needed.
2. When invalid data is detected in a write trigger during an ADD,
the ADM-CREATE-FIELDS comes back disabled.
3. In tableio.i, event adm-enable-fields, in cases where initial
lock is SHARE-LOCK or EXCLUSIVE-LOCK, the FIND CURRENT record
has no NO-WAIT option.
4. A SmartFrame with enabled fields, and have several instances of
this frame on different pages, running init-pages in the
local-initialize of pages, the page that you originally
initialized will have the widgets disabled.
5. If you have a SmartFolder with multiple pages and each page has
a viewer with fields from the same table. If you select add, and
select a page you haven't previously viewed and then select
cancel, the fields on that page become disabled.
6. When selecting Add from a SmartPanel, the fields in the
SmartViewer aren't cleared, the values for the last selected
record are displayed.
7. When SmartObjects linked to each other with a record link, and
there are no records available in one of the objects in a link,
the viewer isn't cleared, but displays data from the previous
record.
8. When two viewer are group-assigned, even though the first causes
the record to be added and exclusive-locked, the second causes
the current-changed method to be dispatched in order to upgrade
the lock, which shouldn't happen.
9. When doing an ADD, and data failed validation, the CANCEL button
doesn't cause the data to be cleared, so the cancelled data is
displayed, and the two viewers are not in sync.
10. When using foreign keys in a SmartViewer that is linked to a
SmartPanel, if the instance attributes are changed to
SHARE-LOCK or EXCLUSIVE-LOCK, error 2129 results and no records
appear in the SmartViewer. Even if the instance attributes are
changed back to NO-LOCK, the error continues.
11. If you have a SmartWindow with a Navigation SmartPanel on page
0, a SmartViewer and SmartQuery on page 1, and nothing on page
2, the Navigation SmartPanel is not disabled when you switch
to page 2 though its link is disabled, so it does nothing
when on page 2.
12. If two SmartBrowsers are linked through a record pass-through
link, if one is the master browse and the other is the detail
browse, when updating the detail browse and then moving to the
master browse to another record, the detail browse does not
reflect the records for the new master browse.
13. Setting multiple attributes in set-attribute-list only set
the first attribute and skipped any additional being set.
14. Adm-create-record contains a ROWID function. When using an
Oracle Dataserver the ROWID function causes the record to be
created immediately and it isn't possible to enter data into
the fields. Therefore, any fields that are mandatory will
raise error 1444.
15. SmartViewer contents are not cleared when the Add operation is
cancelled, when the record-source query did not contain a record
before the Add operation was started.
Progress Software Technical Support Note # 17372