Readnext getting lost (AREV Specific)
At 01 APR 1998 10:56:11AM Dan Houlihan wrote:
We're experiencing a very intermittent problem where the READNEXT fails. It is very hard to isolate because we can not reliably reproduce. We have discovered that in one instance, the READNEXT reset itself to pointing to an earlier key within the segment of the LISTS record. For example, the READNEXT returned the 30th key from the LISTSREC*6 record, then started returning previous keys from that segment.
This is happening on our configuration using an NT 4.0 server with NT Services (v1.5) and the NPP. We are using NT 4.0 workstations. I think it only happens when there are multiple segments affiliated with the key list.
We have never experienced this when running from a Novell 3.12 server using the NLM. Curious, eh?
Please help!!!
At 02 APR 1998 05:06AM Steve Smith wrote:
Just a thought, but is the file BTree indexed? If it is then you may need to rebuild the index.
Steve