>Does anyone have any inforamtion about this error? Does Files=Whatever in config.sys in Win95 have any affect.
>
>We have an application written in VFP3.0 that communicates with up to 30 devices through a serial port and an RS232/RS485 adapter. This application needed to work in Windows3.1 and Win95 so we wrote two DLL's that call windows API functions depending on which operating system is in use. They are straight calls. The only reason we wrote DLL's was because VFP does not handle or pass structures.
>
>In most cases everything works fine but customers complain about this error occasionaly. We have told them to increase the Files setting and reboot. I suspect that it is actually the reboot that fixes the problem. It seems to occur mostly when there are communications errors.
>
>This error completely bypasses our error handler so we don't know what code is barfing and have no way to collect clues. We have not found a way to duplicate the error here.
>
>Please help?
Dan,

I can't really help with the solution but I can explain the error. Error ## reporting error ## is equivalent to Fox saying "I am choking on a chicken bone, but I cannot tell you that I am choking on a chicken bone because I am choking on a chicken bone." IOW, Fox's memory is hosed and it is in a unrecoeverable situation that is so bad it doesn't even know what situation it is in. I would also suspect something in the dll's or fll's that is somehow clobbering fox's memory under certain error conditions during communications.