Hi all. A couple of months ago I posted a strange experience where a customer was experiencing an Internal Consitency Error when trying to reindex a very large (100 Meg +) file using FoxPro 2.6. We were able to make the problem go away by reducing the memory on his Win 98 machine from 128 Meg to 96 Meg.

Last week, I had another customer who was having the same type of problem on a Win Me machine. In a completely different application, when the application tried to create an index on a very large file, foxpro generated an ICE error. It had been doing this for a couple of months, so the user had been performing that operation on another computer. I swapped her 128 Meg of memory for a 64 Meg piece and the problem went away.

I present this info as a heads up in case anybody else sees it and also a question. Can anyone explain this behavior? Is there a better work around? I don't want to tell customers they have to have less that 128 meg!