Re: rgetmsg

finderr 100 shows me the duplicate value message. finderr -100 also shows me this. finderr +100 shows me a no matching record message (i.e. not found). Apparently finderr assumes a negative value unless otherwise specified. I'm not sure about rgetmsg() but if it accepts the message number as an integer then it may always assume a negative number, dealing only with messages categorized as errors. Art S. Kagel wrote: > > Henry A.L. Wollman wrote: > > > > How come rgetmsg returns the wrong description for an error code 100? It > > should be "not found" but instead returns something about a duplicate > > value on insert or update of a unique key. > > > > Are there other error codes for which rgetmsg returns the wrong > > description? It seems that even the manual as far back as several years > > ago has the wrong message for a 100. Aren't these things ever fixed? Is > > rgetmsg not a reliable function? Must I write my own? > > There is nothing to fix since nothing is broken! > > Rgetmsg does not return the wrong message. SQLNOTFOUND, or 100 is NOT > an error, however, there IS an ISAM error -100 which is described as: > > -100 ISAM error: duplicate value for a record with a unique key. > > It is a convenience that finderr and rgetmsg return the message whether > you enter the message number as positive or negative, but remember that > ALL error message numbers are negative! SQLNOTFOUND is an INDICATOR > that there is no more data to fetch NOT and error caused by fetching > beyond the end of the select set. > > Art S. Kagel ---------------------------------------------------------------------- John H. Frantz Power-4gl: Extending Informix-4gl john@rl.is http://www.rl.is/~john/pow4gl.html