>Thanks Al for your recommendation...
>
>Does that mean that the error that is encountered (which is very much hardware related sounding)has really nothing to do with the computer equipment?

Since the introduction of the 80386 processor, x86 and compatible processors have built-in hardware that helps "protect" memory that one application or process is using, from being accessed or overwritten by another application or process.

Windows makes use of this hardware. If Windows detects a program trying to access memory it doesn't own, it throws a "memory protection" error and shuts down the offending program.

I have seen FoxPro cause these errors if the files I described earlier get corrupted and FoxPro tries to use them anyways. Since your program was working fine, it's most likely not a bug in FoxPro itself or in your program logic (the latter shouldn't cause a protection fault anyways, it should be trapped as a FoxPro error). So, file corruption is one thing to look at.