Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 07 DEC 1999 05:41:45PM Chris Miller wrote:

I'm getting an index update error pertaining to a record that has been deleted weeks ago (deleted in order to solve this problem, in fact). I've search for evidence of this record in just about all of my AREV files (data, index, other), and cannot find any. Indexes often update normally, apparently going around this bad record, but sometimes the bad record pops up and crashes the workstations. I am wondering if some network cache or file contains the bad update information. Is there any way to clear all pending index transactions and/or buffers, queues, etc?

This is AREV 2.12 on NLM


At 07 DEC 1999 06:21PM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:

What makes you say it's related to a specific record? Not doubting, just fishing for more information? Tempted to say a dodgy relational is bring it back.

[email protected]

Sprezzatura Group

[/i]World leaders in all things RevSoft[/i]

www.sprezzatura.com_zz.jpg


At 08 DEC 1999 09:29AM Chris Miller wrote:

Here's the error (between ======== lines)

=================

Fatal Error Writing DATA11337WILSONDAVIDJAMESSOUTM11337MCDPUGALL164298-54 –FS466———————– Linear Hash Client/Server No Server Response ================= The contents of the Data line, after the , correspond exactly to the typical record layouts of records in my main file, except that field marks have been removed. I think that the rest of the record appears after the end (after the 54), but it is cut off in the message box. I've asked about this in the Revelation board, but apparently no one knows a thing about this.

I've looked all over the system for a sign of this record (including looking in the ! index file for the data file that used to contain the record), but nothing shows up in my searches, so I am wondering if some reference or part of the record is caught insinde some NLM-related queue or buffer that I do not know how to get to from typical TCL operations.

Thank you for your prompt response to my posting.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/debb7f46bdda79ec85256840007cac13.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1