I’ve seen this issue as well, and stopped putting expressions in the data side of the INSERT statements. In my case, I may have 4-6 temporary tables defined and holding lots of data, with a cursor against one of them and the INSERT working against another.
Emmitt Dove Converting Systems Architect Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, January 20, 2011 11:56 To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Error 2136 Jan: I've seen this error when I'm doing an Insert statement, and am inserting a calculation/concatenation rather than using a variable. Because of seeing this error in the past, I now do the following: SET VAR vText = ('A change was made on' & ctxt(.#DATE) & 'by the user' & .xvUser) INSERT INTO log (invoiceno, message) SELECT invoicno, .vText FROM .... rather than embedding the vText information right into the "insert" syntax. Karen This error can also occur if there is a missing or mis-matched variable type or value on one particular record that causes an expression to fail. I’d look carefully at the data in the last of the 60 tasks which finished properly and at the data in the first record that did not. Sami
