RE indexes

[flowersoft at compuserve.com]

-----Original Message-----
From: filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com
[mailto:filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com]
On Behalf Of Richard Kreiss
Sent: Friday, July 01, 2011 11:36 AM
To: 'Filepro 2 List'
Subject: RE indexes

Interesting problem:

A client was running an output and towards the end of the output run got the
following:


*** A filePro Error Has Occurred ***

Fatal error

On File: F:/filepro/l_doctor/index.B

Invalid index.
Run Index Maintenance to rebuild the index.

This is a single field index on a 4 character numeric field.

When I enter the file and use index B to get to a record, no problem.

When I go to another file which does a lookup to this file using index B no
error - this is in clerk.

Why would a lookup in *clerk not encounter  the same index problem as
*report?

Richard Kreiss

-----End of Original Message-----


I've been having a problem with report (I think Nancy P. has also
experienced this problem) in that it will select, let's say, 300 records and
blow out after printing just one, or 50 or 290. The number varies. No errors
on the screen, nothing.  You can then run the report again, without making
any changes or getting out of filePro, and the report will run perfectly to
its conclusion.
I have no idea what can be causing this.  It doesn't happen to all of my
customers, just some but enough of them for me to know there is something
going on.
I thought it might be too many open files, but doing a 'close' does not
help.  Might be some sort of segmentation violation (this is Windows
however) but there is no message on the screen.  The program just terminates
abruptly.  Happens with both report and dreport versions 5.0.14 RN9 and DN9.

This is a royal pain, especially when running eom statements.  The
statements might only run to the letter C or G or N and then they have to be
generated again.  This, besides wasting a lot of paper, makes the customers
question whether the program generated statements for all the customers that
needed to receive one.  I've never been able to duplicate the problem, even
when using the customer's data, but I have seen it happen enough times in
their systems to know it is not something they are doing wrong.
I also have the program re-build all the indexes involved before running the
report, so it should not be an index problem.



_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes
http://mailman.celestial.com/mailman/listinfo/filepro-list