Kbase P98242: Disabled navigation buttons when query has been opened by findRowWhere()
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/06/2005 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics 2.1A
SYMPTOM(s):
Choose a navigation button in the navigation panel
Button in Navigation panel are in wrong state (disabled while the action should be available)
Just an SDO and a SDV in a container
The query of the SDO is opened by findRowWhere() (was closed before calling it)
Dynamics 2.1A03
CAUSE:
Known issue, development aware. Note that calling findRowWhere() is a valid way to open a query and jump directly to a given record in one single AppServer hit. This is particularly interesting when trying to obtain the best performance in large containers.
Note also that the problem does not occur if:
-The query of the SDO has been opened before calling dinfRowWhere() (such as with the SDO openOnInit property set)
or
-There is also a browse in the container (which leads to having a query opened at some point, see the DataQueryBrowsed SDO property)
FIX:
The problem with the following work around is that there is no way to actually open the query by calling of findrowWhere() so it would open the query and directly jump to a given record in one single AppServer hit.
Make sure the query is opened before calling findRowWhere(). One may want to check the value of the SDO property QueryOpen, and not call openQuery() before findRowWhere() if the property is set to NO.