Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Need Command/Call to Kill Running Excel Instance
Message
De
20/04/2010 10:53:22
Bill Drew
Independent Consultant
Chicago, Illinois, États-Unis
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
COM/DCOM et OLE Automation
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP
Network:
Windows XP
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01461076
Message ID:
01461108
Vues:
57
Really appreciate it.

In my data work -- which seems to take up the majority of my time --- I find myself with sitting a on 3 legged stool to milk the data. (VFP to automate Excel and to make SQl Server calls). The C Sharp programs also figure in -- but I haven't yet picked up as many ways to integrate data from a Winforms screen.

>Bill,
>
>Check http://www.berezniker.com/content/pages/visual-foxpro/check-if-exe-running-and-optionally-terminate-it
>
>>I do a lot of Excel automation. So much that I have a standard stack of commands that I use over and over. oExcel = CreateObject("Excel Application") etc etc. Make an oBook object. Make an OSheet object. Get number of used rows. Iterate through the rows. Do something with the data. Close the Book. Quit Excel. and set the oExcel object to NULL.
>>
>>As I am writing the programs I invariably have bugs somewhere in the process. In those cases where the program never makes it to the final lines of setting the oExcel object to NULL, I have to go to the task manager to kill the instance before restarting.
>>
>>Is there an API call or command that I can use at the beginning of my programs to check for a running instance of Excel and to shut it down before starting a new one. Or (just thinking of another way) should I put the code into a try catch construct? The disadvantage of Try Catch is that interactive debugging is hobbled.
>>
>>Thanks.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform