Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Cannot Print Reports
Message
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Miscellaneous
Thread ID:
00706346
Message ID:
00706352
Views:
15
>Hi,
>
>This is more of a systems question.
>
>I have a print button on one of the forms and clicking this will create a report and bring up the print dialog box.
>
><<
>
>select mytable
>myrec = recno()
>Report Form MyForm Noconsole to printer prompt for recno()=myrec
>
>>>
>
>We have a few employees who work from home(use a Frame Relay Line and connect via a Terminal Server). While they have been able to print from other applications like Word/Excel, all on a sudden, they haven't been able to print from the FoxPro application.
>
>On clicking the PRINT button, it brings up the Print dialog box, and the users selct OK, and the output seems to be going to the printer. But nothing prints at the printer and when we look at the the Print status on the printer, the port number seems to be a blank.
>
>Any help would be appreciated.

It is exceedingly likely that you need to adjust the TSAC or RDP client settings so that WTS will use the local default printer as the Terminal Server default printer; you'll need to load the drivers for each of the printers on the remote clients on Terminal Server (bring up the Printer dialog, and without selecting a printer, right-click and select Server Properties, and add the printer driver to the list of known printer drivers.)

Since the range of printers to be supported will be large, and may involve multiple different port IDs, you'll want to clear out the Expr, Tag and Tag2 field memos of the first record of each of the FRX files that will be printed to the local printers. In addition, you'll need to install the local printers on Terminal Server Remote port IDs on Terminal Server so that they get mapped accordingly and assigned as the default printer.

It's a bit of a cumbersome task if there are lots of different local printer types involved, and if a custom paper size is involved (a problem I have with some of my WTS clients that run label printers locally) you may have a few additional gyrations to go through. The TS Administrator really ought to manage this issue for you.

>
>Thanks.
>
>Ria
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform