Re: SQL statement error number -999
Posted in 2007
run `finderr 999` from the command line. It returns: -999 Not implemented yet. This error means the functionality being exercised is not currently implemented. Check the documentation and release notes that describe this current restriction in this particular release for this product. If this condition is not described in the regular documentation or the release notes and recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com. Which is somewhat ambiguous unless you know what the SQL was that generated the error. The 4GL code should provide some insight into the cause of the error. In the past I've seen this error linked to BOOLEAN and LVARCHAR (opaque) datatypes located on remote servers, but there are surely other causes. Basically the error tells you that you're attempting to perform an action that Informix does not have any code containing instructions on how to do what you've asked it to do. DL ----- Original Message ---- From: Randall Young (ADE) <Randall.Young@arkansas.gov> To: informix-list@iiug.org Sent: Friday, October 12, 2007 12:52:08 PM Subject: SQL statement error number -999 <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue;text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {color:purple;text-decoration:underline;} span.EmailStyle17 {font-family:Arial;color:windowtext;} _filtered {margin:1.0in 1.25in 1.0in 1.25in;} div.Section1 {} --> I am trying to resolve this error number in a 4gl program. I have contacted my DBA but he is at a Friday lunch. I have grepped the release notes for 999 and come up with several hits but nothing seems to reference my situation, I am using IDS 9.40.UC6 and C4GL 7.32.UC2. I get the error when I query a 4gl form and return only one row. I then update the row successfully. When I press an N to get what I think is a non exixtant next row, I get the error. I would expect to be told that there are no more rows. Has anyone experienced this situation? Thanks for your help. -- Randall Young randall.young@arkansas.gov