Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Best way to Handle Processes
Message
De
01/11/2001 23:46:47
 
 
À
31/10/2001 13:08:15
Steven Dyke
Safran Seats USA
Texas, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00575752
Message ID:
00576572
Vues:
15
>In my app I need to create postscript files of drawings for viewing in a workflow signoff process. Before the initiator can effectively pass a drawing to the next step the postscript files must exist. These postscript files are generated by using Run command(WScript.Shell) to act on a plot process in our Cad system. Sometimes the process takes a while. In order to make sure the ps files have the proper name which the plot process can't do, foxpro has to give it a name. This means that the run has to complete before naming, coping, deleteing old file, do over with all sheets. Anyway while this is going on the user is stuck from a few seconds(noy bad) to minutes(not so good). Do any of you have sugestions?

You can use my API_APPRUN class to start a process asynchronously and check it's progress and determine when it terminates by intermittently polling the status, as well as offering synchronous processing. It's in the Files section.
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
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform