2.6 Reports Freezing Computer Randomly

[DaleFrench]

Hello all, I have a customer that uses a 2.6 application for her check unit. Every three or so records she enters and then prints a report, the computer freezes with the blank white paper screen and hourglass. She has to reboot. I am using the REPORT command. What is strange is that this just started happening without any problem updates, printer, or workstation changes. They use Windows 98 Operating systems. Here is what I have tried.

1. Deleting and recreating indexes.
2. Deleting all Foxuser files.
3. Deleting all Esl files except for one in use.
4. Patching the Esl file with Dzpatch.exe
5. Reinstall the printer driver.
6. Replacing the HP 1100 with a standard HP deskjet.
7. Clearing the envirement on in modify reports.
8. Moving the application and data to a different computer
with a different physical printer.
9. Adding LOADDEVICE=HIGH in the config file.
10. Recompiling their application from scratch.

One thing I noted was when one record locked up it would lock up consistantly when printing the same report. It is not just a single report that is making the problem. It is
several.

Why would this just start happing after months of no problems? What should I do?

Any help would be greatly apprieciated.

Thanks in advance.

Dale

 

[DSummZZZ]

It sounds like you've done most if not all of the necessary things to get rid o f most troubles. A couple other things maybe,
Have you re-modified the reports for the new printer driver or at least removed the printer specific info from the report form?
Have you deleted any .TMP files left laying around?
Is there sufficient rights to wherever the .TMP files are written?


-Dave S.-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[DaleFrench]

Thanks DSumZZZ for the helpful information. I haven't even thought about tmp files. How would I find out where they are saved to? From the source code or maybe the config file?
I will try that tommorrow and also check out the link you gave me.

Thanks again.

Dale

 

[DSummZZZ]

There may be an entry in the config.fp? file. But if not, they can go to whatever Fox thinks is the temp directory. Go to a command (DOS) prompt and type SET. Look for the TEMP or TMP setting there.
Or from Fox command window, do a ?GETENV("TEMP&quot to see where it may be pointing.


-Dave S.-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm