(GRX) Memory could not be read from UPDATE/SOLUTION (reprise)

[Chris Sellitto]

This is a repeat of a post I sent recently.  I was wondering if anyone had received it.  Anyway, here it is.
 
Hello all,

I just wanted to give you an update, and possible suggestion for an error message that had been annoying us for a while. I had posted about it a few months ago without much luck (thanks for all the replies), but the problem had subsided for a little while, then recently cropped up in one of our offices on a consistent basis. The error message read as follows......

The instruction at 0046f22a referenced memory at 20202020. The memory could not be read from.

Well we tried many different things to resolve this issue (config.sys, config.nt and so on). Mind you, it is costing us serious production time. Well after pulling out the little hair I still have, I was looking at the size of the index files for one of the databases, and noticed that 2 of the indexes looked unusually larger than the rest. I took a look at the same index files in our home office, and their sizes were more in line with the rest of the indexes, so I reindexed the 2 indexes in our other building, ran the process that was consistently crashing with the above error, and low and behold, it worked. No more memory errors.

I was wondering, does this make sense to anyone, and could anyone explain why a corrupt index would manifest itself as a memory reference error.

Thank you in advance for any insight on this issue.

Christopher Sellitto
VP Computer Operation
Guaranteed Returns
Holbrook, NY

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.celestial.com/pipermail/filepro-list/attachments/20061005/9a3cccce/attachment.html