G
Garry Hall
Guest
Given that this is a NO-UNDO temp-table, my guess at what is happening here is that there was some other error that caused the AVM to leave a block without doing the indexing. You defined the temp-table as NO-UNDO, meaning changes (even incomplete changes) don't get backed out in the event of undo.This is simple enough to reproduce: DEF TEMP-TABLE tt1 NO-UNDO FIELD f1 AS CHAR FIELD f2 AS CHAR FIELD f3 AS CHAR INDEX ix1 IS UNIQUE PRIMARY f1 INDEX ix2 IS UNIQUE f2 INDEX ix3 f3. DEFINE VARIABLE ictr AS INTEGER NO-UNDO. DEFINE VARIABLE ival AS INTEGER NO-UNDO. DO TRANSACTION: DO ictr = 1 TO 5: CREATE tt1. ASSIGN tt1.f1 = FILL(CHR(64 + ictr),5) tt1.f2 = tt1.f1. tt1.f3 = tt1.f2. IF (ictr = 5) THEN ASSIGN tt1.f3 = "Error" ival = INT("error"). END. END. FOR EACH tt1: DISPLAY tt1. DELETE tt1. END. To resolve this particular error, you need to identify what caused the transaction to terminate while updating the temp-table (specifically, updating the chCFGrid field). The cause of the termination is probably specific to RemoteApp. You might try 4GLTRACE:3,4GLTRANS:3 logging, although it is very verbose. The alternative is to not declare the temp-table as NO-UNDO, and incur any performance penalties for it. Depending on how intensively this temp-table is used, that performance penalty might be inconsequential.
Continue reading...
Continue reading...
