Quit a Process

[Hannes214]

Hi

How can I quit an other process from a vfp-application?
I want to kill the process abc.exe at a special time and run an other application...

Can anybody help me?

IT-Management
( FoxPro-Newbi ) )

 

[Mike Lewis]

You would need to get the process handle of the application to be terminated. If you can do that, use the TerminateProcess() API:

DECLARE INTEGER TerminateProcess IN kernel32;
    INTEGER nHandle,;
    INTEGER nExitCode

TerminateProcess(<put process handle here>, 0)

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk

 

[Hannes214]

Thx .. but how can I get the process handle??
I only have the name of the process...

IT-Management
( FoxPro-Newbi ) )

 

[ChrisRChamberlain]

Hannes214

The following snippit will kill any instances of process2kill.exe

[COLOR=blue]oManager = GETOBJECT([winmgmts:])
cQuery = [select * from win32_process where name='process2kill.exe']
oResult = oManager.ExecQuery(cQuery)
FOR EACH oProcess IN oResult
[tab]oProcess.Terminate(0)
NEXT
oManager = .NULL.
oResult	= .NULL[/color]

FAQ184-2483 - answering getting answered.​

Chris
PDFcommander[sup]tm[/sup].net
PDFcommander[sup]tm[/sup].com

 

[Hannes214]

Thx Cris

But I have the "old" problem, that I can't use [winmgmts:]under VFp 6.0 ...

IT-Management
( FoxPro-Newbi ) )

 

[alvechurchdata]

If you pass the title of the window to FindWindow from the Win32 API then it will return the handle. You can then use PostMessage to send a close message (0x12) to that window.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[Hannes214]

I want to kill a screen-saver at a special time...
so I dont think, that it has a titel... and I dont know the titel...

IT-Management
( FoxPro-Newbi ) )

 

[alvechurchdata]

I want to kill a screen-saver at a special time

Sorry - can't help you there.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[rob444]

Perhaps this link will help you:

http://www.news2news.com/vfp/?group=58&function=133

Rob.

 

[rob444]

This is a better one:

http://www.news2news.com/vfp/?group=58&function=225

Rob.

 

[Hannes214]

Ok .. I find a solution that works with VFP 6.0

Local lcRemoteComputer, lcAdminUserName, lcAdminPassword, loSWbemLocator, loSWbemServices

lcAdminUserName=""
lcAdminPassword=""
lcRemoteComputer = "."

loSWbemLocator = CreateObject("WbemScripting.SWbemLocator")
loSWbemServices = loSWbemLocator.ConnectServer(lcRemoteComputer, "root\cimv2",lcAdminUserName,lcAdminPassword)
lcolSWbemObjectSet = loSWbemServices.InstancesOf("Win32_Process")

FOR EACH loProcess In lcolSWbemObjectSet
	IF TRANSFORM(loProcess.Name) = "blackshow.scr"
    	*Messagebox("Name: " + TRANSFORM(loProcess.Name)+CHR(13)+"Process ID: " +;
    	*			TRANS(loProcess.ProcessID)+CHR(13)+"Prozess wird beendet.")
    	loProcess.Terminate(0)
    ENDIF
NEXT

IT-Management
( FoxPro-Newbi ) )

 

[Mike Lewis]

Hannes,

Your solution seems to work, but Im curious ... what exactly is WbemScripting? I've not come across it before. Also, is the reference to a "remote computer" significant? It works OK on a local machine.

I also discovered that loProcess.Name is case-sensitive.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk

 

[DSummZZZ]

Mike,

From MSDN:
In summary, WBEM is not browser-based, nor is it a user interface (UI) tool, a data repository, a network management protocol, a component model, or a registry, directory, or file system replacement. WBEM is an initiative that proposes a set of standards for managing the enterprise network

Evidently, WMI is a portion of WBEM.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Mike Lewis]

Thanks for that, Dave. I now know what WBEM is not <g>. I'm not sure how an "initiative that proposes a set of standards ... " is also a COM server, but I'll let it go at that.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk

 

[DSummZZZ]

Yup. Typical doublespeak from someone trying to invent a standard.
I thought the "what it isn't" description was quite entertaining.
The "what it is" part, I don't think anyone really knows.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm