Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Developer's default printer information
Message
De
15/09/2000 09:41:37
 
 
À
15/09/2000 08:29:45
Mark Defee
R&K Engineering, Inc.
Roanoke, Virginie, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire de rapports & Rapports
Divers
Thread ID:
00416795
Message ID:
00416828
Vues:
37
> I have a problem with the default way that Visual FoxPro's Report Designer saves the developers default printer settings in its reports. I have done some research on this and have discovered where this information is stored in the .FRX file and know how to clear it. This method of clearing out the Tag and Tag2 fields is a real pain with 75+ reports in my application and it is required because with this information stored in the report, using the "SET PRINTER TO NAME \\printserver\printer" command to send the report output to multiple locations does not function properly at the client sight. Additionally, I am in a multi-developer environment with source control software in place and this makes the process of catching all possible oversights of removing these field contents at compile time a real nightmare.
>
> My real question is simply this, am I overlooking a way to turn off this "wonderful" default of VFP saving this information in the report? If not, are there any suggestions around this? Thanks.

VFP6 provides a ProjectHook class that can be used to trigger actions immediately before building (strangely named BeforeBuild) - you could add code to your working Project-processing that routinely ran through all the FRXs in the project and stripped the printer information immediately before producing the release build.
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
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform