Re: -266 Error When Logging Is Enabled

The fix for PTS 172334 changed the error message from -266 to -255 (Not in transaction) because -266 is misleading. So using a newer version won't solve your problem :-( insert/update/delete within a hold cursor must be always started in a transaction. Adam Tauno Williams wrote: >I have some 4GL applications that where written with a database with >logging disabled and I would like to enable logging on that database. >However when I do so the 4GLs still work so long as you don't attempt to >modify data; as soon as you attempt to modify data you get an "-266 >There is no current row for UPDATE/DELETE cursor." error. Turning >database logging back off (of course) resolves the problem. > >Are these 4GLs a lost cause or is there some work-around? >sending to informix-list > >