Running FoxPro Applications with DESQview

Last reviewed: April 17, 1995
Article ID: Q87475
The information in this article applies to:
  • Microsoft FoxPro for MS-DOS, versions 2.0, 2.5 and 2.5a

SUMMARY

The text below details how to configure Microsoft FoxPro applications under DESQview, including DESQview program information file (PIF) settings.

MORE INFORMATION

Each FoxPro application that runs under DESQview must have a CONFIG.FP configuration file that specifies a unique location for its resource and temporary files. Using the same FOXUSER.DBF file for multiple applications causes difficulties such as "cannot update file" errors. Sharing the same .OVL file causes problems when FoxPro exits.

To avoid these and other problems, use the following PIF settings:

  1. Use the -C option in the PIF Parameters line to specify which CONFIG.FP file is used by each application.

  2. Adjust the PIF settings for the amount of memory each FoxPro application uses. The standard PIF settings are as follows:

          Memory Size: 500
          Maximum Program Memory Size: 640
          Maximum Expanded Memory Size: 2048
    

  3. The Run In Background and Share CPU When Foreground options can be used to run more than one FoxPro application simultaneously. However, the currently selected window may operate slowly in this environment.

  4. Specify NO for the Allow Close Window Command setting. This prevents the user from abnormally terminating a FoxPro application from the DESQview menu.

Notes on Using DESQview

  • To activate an application without using the DESQview menu, redefine the DESQview key to another key combination, for example, SHIFT+CTRL. For more information on redefining this key, refer to the DESQview manual or contact Quarterdeck Technical Support at (213) 392-9701.
  • If the mouse leaves a trail on the screen, activate the Setup DESQview window and select the proper mouse type from the listed options.
  • Do not run disk-organization utilities, such as CHKDSK /F and VOPT, from Big Dos while a FoxPro application is running.

NOTE: Some products mentioned in this article are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.


Additional reference words: FoxDos 2.00 2.50 2.50a DESQ View droppings
KBCategory: kbsetup kb3rdparty kbenv
KBSubcategory:


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 17, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.