Microsoft KB Archive/109300: Difference between revisions

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - "<" to "<")
Line 1: Line 1:
{|
{|
|width="100%"|
|width="100%"|
= SET PDSETUP TO &lt;DriverName&gt; Changes Only Existing Drivers =
= SET PDSETUP TO <DriverName&gt; Changes Only Existing Drivers =


'''ID: Q109300'''
'''ID: Q109300'''
Line 13: Line 13:
== SUMMARY ==
== SUMMARY ==


In FoxPro for Windows, the SET PDSETUP TO &lt;driver_name&gt; command selects only an existing MS-DOS style printer driver. It cannot edit an existing MS- DOS style printer driver or create a new one.
In FoxPro for Windows, the SET PDSETUP TO <driver_name&gt; command selects only an existing MS-DOS style printer driver. It cannot edit an existing MS- DOS style printer driver or create a new one.


== MORE INFORMATION ==
== MORE INFORMATION ==


To use the SET PDSETUP TO &lt;driver_name&gt; command in FoxPro for Windows, the current resource file (by default FOXUSER.DBF and its associated memo file, FOXUSER.FPT) must already have an MS-DOS style printer driver loaded. This MS-DOS style printer driver must have been previously created by FoxPro for MS-DOS.
To use the SET PDSETUP TO <driver_name&gt; command in FoxPro for Windows, the current resource file (by default FOXUSER.DBF and its associated memo file, FOXUSER.FPT) must already have an MS-DOS style printer driver loaded. This MS-DOS style printer driver must have been previously created by FoxPro for MS-DOS.


FoxPro for Windows normally uses Windows printer drivers for all its printing. Windows printer drivers are changed through the Windows Control Panel.
FoxPro for Windows normally uses Windows printer drivers for all its printing. Windows printer drivers are changed through the Windows Control Panel.


Only use the SET PDSETUP TO &lt;driver_name&gt; command with character-based reports that were created in FoxPro for MS-DOS.
Only use the SET PDSETUP TO <driver_name&gt; command with character-based reports that were created in FoxPro for MS-DOS.


NOTE: The SET PDSETUP &lt;driver_name&gt; command has no effect on Windows printer drivers.
NOTE: The SET PDSETUP <driver_name&gt; command has no effect on Windows printer drivers.


For more information about using Control Panel to change Windows printer drivers, query on the following words in the Microsoft Knowledge Base:
For more information about using Control Panel to change Windows printer drivers, query on the following words in the Microsoft Knowledge Base:

Revision as of 15:02, 20 July 2020

SET PDSETUP TO <DriverName> Changes Only Existing Drivers

ID: Q109300

2.50 2.50a 2.50b WINDOWS kbprint kbtool kbprg

The information in this article applies to:

  • Microsoft FoxPro for Windows, versions 2.5, 2.5a, and 2.5b

SUMMARY

In FoxPro for Windows, the SET PDSETUP TO <driver_name> command selects only an existing MS-DOS style printer driver. It cannot edit an existing MS- DOS style printer driver or create a new one.

MORE INFORMATION

To use the SET PDSETUP TO <driver_name> command in FoxPro for Windows, the current resource file (by default FOXUSER.DBF and its associated memo file, FOXUSER.FPT) must already have an MS-DOS style printer driver loaded. This MS-DOS style printer driver must have been previously created by FoxPro for MS-DOS.

FoxPro for Windows normally uses Windows printer drivers for all its printing. Windows printer drivers are changed through the Windows Control Panel.

Only use the SET PDSETUP TO <driver_name> command with character-based reports that were created in FoxPro for MS-DOS.

NOTE: The SET PDSETUP <driver_name> command has no effect on Windows printer drivers.

For more information about using Control Panel to change Windows printer drivers, query on the following words in the Microsoft Knowledge Base:

   control and panel and run and printer and foxpro

Additional reference words: FoxWin 2.50 2.50a 2.50b _pdparms KBCategory: kbprint kbtool kbprg KBSubcategory: FxenvFoxuser

Keywords          : FxenvFoxuser 
Version           : 2.50 2.50a 2.50b
Platform          : WINDOWS

Last Reviewed: May 1, 1996
© 1999 Microsoft Corporation. All rights reserved. Terms of Use.