>>>I have a POS system Installed on a 586 Cyrix Computer and the problem is as follows:
>>>
>>>The system has a main database where all the sales information is stored.
>>>Every now and then this file gets corrupted and when the system attempts to insert a new record
>>>It halts and the system crashes. To correct the problem I create a new file with the same structure and copy the contents from the corrupted file onto the new one.
>>>
>>>When the file is corrupted I can access the information on it and append new records from the command window; but when I try to append from within a program the system halts and I have to reboot the computer. Have this ever happened to any one?
>>>
>>>I have checked for virus and as far as I can see there is none. The computer is new and I installed win 95 and the system my self there is no other software installed on the computer. The computer where the system was developed has never failed nor have a problem like this.
>>>
>>>Can any one help me?
>>>
>>>Thanks.
>>A few questions...
>>1) What is the configuration of the computer the system was developed on?
>>2) How much, and what type of memory do you have on the new system?
>>3) What version of WIN95 are you running? Are you using the FAT32?
>>4) What version of Foxpro are you using / system developed in ?
>>
>>It sounds to me like either a memory or WIN95 problem, but need more configuration info to troubleshoot.
>
>Hi thanks for answering so fast.
>
>The POS was developed on a Packard Bell Pentium 75 computer with I upgraded to WIN95 about 8 months ago I have 24MB extended memory the new system has 16mb extended memory and is using the same win95 version that I have I am not sure about FAT32 but you raised a very good question I've checked my CONFIG.SYS and found that I have FILES = 100. I don't have the other computer at hand but I figured it doesn't have this line on the config.sys sense I did not put it there. Perhaps this is the problem?
>
>The system was developed in VFP 3.0
>
>Again thanks.

I don't see where the line in your config.sys would have much to do with this problem, but I could be wrong. Stranger things have happened... Just a couple of notes, as you may well know, 16MB is pretty much the minimum for memory when it comes to VFP. I am using a P133 with 32MB at work, and I have some serious performance problems when handling large tables, ie.; 100,000 or more records. This is especially evident when there are numerous objects loaded into memory. At 16MB, VFP is going to be writing massive amounts of data to the hard drive, since the memory configuration is at a minimum. This has led to corruption problems for myself before.

Second, try to check that your 586 processor is not overheating. I have heard that the Cyrix chips have a tendency to do this. Although, this seems to be more prevalent with the 686. One way to check this is by removing the case and watching the system for glitches. This may not be an aesthetic way of troubleshooting, but after living in Arizona for 12 years, it sure works effectively.