>We've recently started seeing Internal Consistency Errors (ICE) in FoxPro for Windows 2.6a when running SQL SELECT queries on fast Pentium III PC's (450 MHz and faster) against fairly large tables (100,000+ records). This problem does not appear when running on PC's of 350 MHz or slower. All PC's are running Windows 95. We are using patched (DZPATCH) versions of FOXPROW.EXE and FOXW2600.ESL that resolved the Divide-By-Zero error on startup we were getting on the 350 MHz machines. The ICE errors occur almost immediately after executing a SQL SELECT command that contains a WHERE clause with one or more non-optimizable expressions. This same query will run fine on all other machines up through 350 MHz. The ICE error will occur regardless of whether the source table(s) are on a network or local drive. The ICE errors have not occurred (yet) when running a SQL SELECT command that is *fully* optimizable or one which simply reopens the source table as a filtered alias. It is also worth
>noting that VFP 6 handles the identical queries without any problems, regardless of processor speed. Unfortunately, upgrading all FPW applications (EXE's) to VFP is not an option in the near term. If anyone else has run into this problem on very fast Pentium III machines and has a solution, I would love to hear about it. I would also be interested in hearing from folks that ARE able to run SQL queries against large tables using FPW on 450+ MHz machines....I'm hoping there is some Windows/PC hardware configuration change I can make to avoid the problem.
>
>Thanks!


I have not heard of this happening in the situation you describe, but I have a KB article on my web site that discusses the most common ICE problems.