Re: isrecnum bug in C-ISAM

Just thought I would point out that there is a (nasty) fix to the problem I pointed out with C-ISAM. Unfortunately, it will only work if the index you are using doesn't have duplicate keys. When you read ISNEXT or ISPREV (with ISSKIPLOCK) and get a return code indicating that the record is locked, you know that isrecnum is junk, but the data returned is correct. Therefore, issue a read ISEQUAL on the key which the ISNEXT/ISPREV read returned. This second read will return not only the correct data, but also the correct isrecnum! -- _--_|\\ Craig Macbride <lhscmc@luxor.latrobe.edu.au> / \\ <s900387@minyos.xx.rmit.oz.au> \\_.--.*/ v