ID: Q153906
2.60 UNIX
kbother kbdisplay
The information in this article applies to:
Sometimes when you port FoxBASE for UNIX applications to FoxPro for UNIX, your systems can become slow and create huge temporary files, filling up their available disk space. In most cases, this behavior occurs when SET DOHISTORY is ON. In FoxBASE, having SET DOHISTORY ON helped programmers determine what caused an error in their programs. The Help file for FoxPro has a caution that reads:
Programs execute many times slower when SET DOHISTORY is ON. DOHISTORY
constructs a temporary file as the program executes because the Command
window is a special type of FoxPro editor session. This can fill up even
a large disk very quickly.
Use SET DOHISTORY only as a debugging aid to isolate particularly
stubborn bugs. Be sure to remove any SET DOHISTORY ON commands from your
programs before you execute or distribute them.
SET DOHISTORY is set to ON.
Remove SET DOHISTORY ON from the program, or issue SET DOHISTORY OFF in the program (the default is OFF).
This behavior is by design.
SET DOHISTORY was included for backward compatibility. Use Trace and Debug to isolate problems with your program.
Help file SET DOHISTORY
Additional reference words: 2.60 FoxUnix KBCategory: kbother kbdisplay KBSubcategory: FxenvOptimize
Keywords : kbenv FxenvOptimize
Version : 2.60
Platform : UNIX
Last Reviewed: May 13, 1998