RE: Dirty read on SCO

set lock mode to wait Murray Wood -----Original Message----- From: Perv [SMTP:null@millsandallen.com] Sent: Tuesday, April 27, 1999 9:01 AM To: informix-list@iiug.org Subject: Dirty read on SCO Subject: Dirty read on SCO Problem: 4gl programs crash with 'row locked' despite having dirty read set. I have encountered this problem running on SCO and Version 7.22 of the engine. At the start of each program I set isolation to dirty read and never reset to any other value. All tables have row level locks. A query on a set of rows will yield the following error SQL statement error number -243. Could not position within a table (informix."tabname"). SYSTEM error number -144. The problem is not so pronounced if I place another dirty read set just before the offending line, but its hell to do this everywhere - surely the initial setting should be held. The same code seems to work fine under HPUX.