Kbase P22603: Limitation with SDB or Lookup against temp-table, rows to ba
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/8/2003 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics 2.0A
SYMPTOM(s):
lookup against temp-table, rows to batch does not work
SmartDataBrowser against temp-table SDO, rows to batch does not work
unpredictable rows are sent into the browse when a new batch of rows is sent
CAUSE:
There is an undocumented ADM2 limitation with Dyn Lookup's against a temp-table and the management of batches of rows. This problem also applies to SmartDataBrowsers against Temp-table SDO's. (or SDV + toolbar + TT-SDO).
When a new batch of rows is sent (pressing the cursor-down or page-down key), unpredictable rows are sent into the browse. This is due to the fact that the ADM2 relies on rowObject.rowIdent that holds temp-table ROWID's. Since the concerned temp-table is created and deleted on the server side at each AppServer hit (PLIP to feed lookup, or TT SDO), then these rowident's are simply not reliable any more.
An enhancement request has been log to document this problem, and to make the ADM2 handle a warning message when the number of temp-table records are greater than rowsToBatch
CAUSE:
Bug# 20030407-013
FIX:
Solution is to either:
1) Use a great value for RowsToBatch (greater than number of TT records)
2) Use a Database Table instead of Temp-table. Note that it is better for performance and more consistent (these records are probably not that temporary after all)