Re: isrecnum bug in C-ISAM

In article <1992Apr13.034933.2354@luga.latrobe.edu.au>, lhscmc@latrobe.edu.au (Craig Macbride) writes: > 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! Why not use ISCURR? I believe that ISCURR reads the record where the file pointer is pointing regardless of what is in isrecnum. Also, this method would work on Unique and Duplicate indexes (it'd be quicker too). DAS -- David A. Snyder @ Snide Inc. - Folcroft, PA Current Release is db4glgen-3.4 UUCP: ..!uunet!das13!dave INTERNET: dave.snyder@snide.com