>Hello,
>
>This ICE is a pain in the #@#@!!@#!!.
>
>I have a FPW 2.6 application that I have loaded on a Win95 box, PII 333, 128MB RAM. I have shared the directory where the runtime executable is located.
>
>When I run the appication on the PII 333, the program starts, however, when I run a SQL that is built into the executable on one of the tables, I get the ICE. Interestingly enough, when I go to another computer that has a mapped drive to the PII 333 directory, I can run the program and run the SQL and do not get the ICE.
>
>I have deleted the FOXUSER.DBF from the directory, I have put RESOURCE = OFF in my Config.fpw and I have DELETE TAG ALL and INDEX ON each of the tables involved.
>
>Why do I get the ICE on the PII box that is hosting the executable, but not on the other computer that has a mapped drive to the PII??
>
>The other computer is a pentium box, a little slower than the PII.
>
>NOTE: I do not think this is the fast pentium bug. I have applied the patch and the executable does start on the PII 333. In fact everything else appears to work OK on the PII. It is just the SQL that is causing the ICE.
>
>This makes no sense to me. Any help will be greatly appreciated.
>
>Thanks,
>
>TFISHER
Where are the temp files going? If specified in the CONFIG.FPW, make sure the directory exists.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer