I am getting the following error when attempting to write to create an invoice:

Logical Error Writing 13525 in file INVOICES FS215 the Quickdex or Rightdex index has been corrupted. You can rebuild the index by executing a "LIST" or "SELECT" command.

For the past week, I had received the error

Physical Error Writing 13519 in file INVOICES

FS152

__

I was able to resolve this second error by following the directions

on this message board. The directions that I used to resolve FS152

were

F5 DICT INVOICES F6 (Option 3 - Quickdex/Rightdex data file)

Answered Yes to popup window B202 "Do you want to remove Rightdex?

When I did this yesterday, problem FS152 went away. I had invoiced the problem invoice.

Today, when I try to invoice some other invoices that were affected by FS152, the error FS215 now occurs.

When I repeat the above remedy:

F5 DICT INVOICES F6 (Option 3 - Quickdex/Rightdex data file)

Answered Yes to popup window B202 "Do you want to remove Rightdex?

I am surprised that it says "INVOICES" has "RIGHTDEX" installed.

I thought that this was turned off yesterday.

Help!!

I am using Advanced Revelation v2.1.

Steve

For a while we had this problem, and it was traced to a user trying to use the zoom key while in the dictionary editor. One false step while zooming (F3) will install a quickdex to the data file(SF3).

A similar problem can happen by confusing the edit toggle (F4) with the dictionary quickdex (SF4).

I don't know if this is your problem, but it's worth checking out anyway.

Thanks for the tip Victor. Will check it out.

I did try something else out. When executing the function to invoice, which caused the original problem FS152 and the new problem FS215, it opens file PRE.INVOICES, creates a new invoice number, moves the picked item into the INVOICES file, then removes it from the PRE.INVOICES file. The new invoice still contains the pick number, which is ok and is used for reference purposes.

Based on this, I decided to remove QuickDex from the PRE.INVOICE file.

I will submit those results in the next posting.

Steve

This is an update to my previous message.

The removal of the Quickdes/Rightdes from the file "PRE.INVOICES" didn't resolve the problem.

Although with error# FS215, I can enter "C" to continue with the invoicing process. Unfortunately, error# FS215 will pop up whenever invoicing is required.

Any help with this problem will be greatly appreciated.

Steve

Log on to SYSPROG and attach the REVMEDIA file on the volume containing your INVOICES file (or set a qfile to it from your regular account).

EDIT REVMEDIA INVOICES*account (where account is the name of the account that owns the INVOICES file).

Using the delete key, remove quickdex.mfs or rightdex.mfs and delimiter if present.

Press F9 to save the record

Log on to your normal account.

DELETE INVOICES %RECORDS%

All the above should happen automatically when you remove a quickdex/rightdex in the dictionary editor. Following these steps, perhaps you can see what is going wrong.

Make sure to back up your REVMEDIA file before attempting these steps in case something goes wrong.

If this doesn't resolve the problem, I've run out of ideas. Maybe there's something in your code.

Might you have an attach image?

akaplan@sprezzatura.com

Sprezzatura, Inc.

I want to thank Victor Engel and Aaron Kaplan for their advice. I also want to thank all of the other Revelation Gurus, who provided their inputs on past unrelated message topics. They provide good reading. It is because of this participation that makes this message discussion group a valuable resource for administrators of Relevelation systems.

I would like to contribute my solution to this problem so that someone else can benefit.

Problem:

Originally, I received error: FS152 Physical Error Writing 13519 in file INVOICES. After reading numerous message threads which pointed to the solution of F5 - DICT INVOICES Enter - F6 - SF3 (Remove QuickDex/Rightdex from data file), I used the same solution.

This appeared to fix the problem. I was able to generate one invoice without error FS152 appearing. On the following invoicing, the error: FS215 Logical Error Writing 13525 in file INVOICES surfaced.

I thought that this second problem was due to the fact indexing was still present. When I repeated the above solution, it appeared that the indexing was still on.

Solution:

In Windows98, I ran a DOS command shell and navigated to the directory where the file Arev.exe was located. Logged onto Revelation as sysprog using the following syntax " AREV SYSPROG /X ."

After logging on, I logged onto the "Sale.Management" menu screen. From this screen, I pressed F5, which brought up the TCL screen.

From the TCL screen, I typed CW LH_VERIFY . The LH_Verify screen popped up. From the Volume field, I pressed F2 to bring up a list of volumes. I navigated to the volume that contained the file INVOICES and pressed

For the file name, I used the * symbol so that I could have it check all of the files on the volume. At this point I wasn't getting a GFE Linear Hash File error message so I decided what the hell because I wasn't getting anywhere.

When LH_VERIFY was finished, it generated an error report to the screen, which showed that frame 984 has some problems, and it indicated that the error was in ther "OV" file. I noted the frame number.

I pressed the ESC key which returned the TCL screen. I entered DUMP INVOICES. The Dump screen came up. I typed 984 then CTRL G. I jumped to frame 984. I screen captured this screen.

After capturing the screen, I pressed CTRL F simultaneously. This started the DUMP FIX process. It asked me for the frame number. I chose ALL. I wanted to fix potential GFEs. The DUMP FIX took less than 10 minutes.

After DUMP FIX finished, I pressed CTRL C to compact the frames.

When it was done, I tested out the fix by printing some invoices. Joila, no problems. I would highly recommend that you print the webpage that discusses GFE errors. Another recommendation, keep daily backups.

Refer to this page before attempting the above procedure:

http://www.revelation.com/WEBSITE/knowledge.nsf/89e60900cf7ebbc8852566f500654ecb/b6f3db8c43454185852563b6006a273b?OpenDocument

Good Luck

Steve

View this thread on the forum...