Re: Accessing 4GL cursors with prepared & executed SQL

In <6d6nj2$hh1$1@nnrp1.dejanews.com> jhannah@mammoth.org writes: >Unfortunately, I am forced to prepare and execute one of my update statements >(due to syntax problems). When I do, the "where current of c_jdate" clause >suddenly becomes problematic: >--- >Program stopped at "phhours.4gl", line number 67. >SQL statement error number -507. >Cursor (c_jdate) not found. >--- Check your release notes for cursor name mangling. This problem occurs because the engine mangles the declared cursor to an internal name, which does not then correspond to the name in the prepared update clause. You can work around the problem by turning the mangling off at compile time, but you need to be aware of the possible repercussions if you do. -- Bryan Tonnet batonnet@phase4.com.au