Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Pete Sass
  Where is Pete Sass?
 Marathon, Ontario
 Canada
 Pete Sass
 To: Mike Gagnon
  Where is Mike Gagnon?
 Pointe Claire
 Canada
 Mike Gagnon
 Tags
Subject: RE: Kill EXE API
Thread ID: 416387 Message ID: 416428 # Views: 40 # Ratings: 0
Version: Visual FoxPro 9 SP2 Category: Win32API programming
Date: Monday, December 29, 2014 1:46:26 PM         
   


> >
> >
> >
> > Hi Mike,
> >
> > Lately I have ran into clients were their IT departments have
> > disabled all scripting on all workstations. Due to this one
> > rather large program has to have all WMI code changed.
> >
> > Pete "the IceMan", from the Great White North of Canada.
> > www.marathongriffincomputers.com
>
> Pete,
> I was just pointing out to Jun that you specified that scripting was not allowed. I have encountered the IT scripting blocking before as well. But I have never encountered the need to kill a process other than I restart a process for a 24/7 application on a daily basis, to handle the memory leaks.
>
> Mike Gagnon


Hi Mike,

This is a unique case involving QuickBooks integration.
QB has the following option that is checked as on when the software is installed.

"Keep QuickBooks running for quick startups" Notice below I have unchecked it!


Unfortunately, not all of QuickBooks is running, but the QB32.EXE is shown running in the
Windows process window. At this point QuickBooks is not fully running and does not even
have a company file loaded.

So our integration software will check for this to see if QuickBooks is running prior to
attempting a connection with integration dll. However, in this state the dll call to connect
will error out as QuickBooks is not really fully loaded.
The dll once called spits out it's own bunch of errors that cannot be trapped back in VFP
so now you have a trashed application EXE with the infamous APPcrash scenario.

If the above situation is sensed, the QB32.exe must be killed and the QB32.exe automatically
re-launched bring the user back to QuickBooks that will now prompt to load a company data file
or login.

For this one irritating reason I need a Kill routine that works 100% of the time or the entire
integration application can totally crap out with this quick startup option set on.
There is no QuickBooks API call to automatically turn this option off so I am stuck.

Pete "the IceMan", from the Great White North of Canada.
www.marathongriffincomputers.com

ENTIRE THREAD

Kill EXE API Posted by Pete Sass @ 12/29/2014 1:40:46 AM
RE: Kill EXE API Posted by Chuanbing Chen @ 12/29/2014 1:55:13 AM
RE: Kill EXE API Posted by Pete Sass @ 12/29/2014 2:09:06 AM
RE: Kill EXE API Posted by Jun Tangunan @ 12/29/2014 2:21:49 AM
RE: Kill EXE API Posted by Pete Sass @ 12/29/2014 3:11:45 AM
RE: Kill EXE API Posted by Jun Tangunan @ 12/29/2014 7:13:26 AM
RE: Kill EXE API Posted by Mike Gagnon @ 12/29/2014 3:12:39 AM
RE: Kill EXE API Posted by Jun Tangunan @ 12/29/2014 7:16:19 AM
RE: Kill EXE API Posted by Pete Sass @ 12/29/2014 12:07:30 PM
RE: Kill EXE API Posted by Mike Gagnon @ 12/29/2014 12:28:36 PM
RE: Kill EXE API Posted by Pete Sass @ 12/29/2014 1:46:26 PM
RE: Kill EXE API Posted by Greg Green @ 12/29/2014 3:44:35 AM
RE: Kill EXE API Posted by Pete Sass @ 12/29/2014 1:22:22 PM
RE: Kill EXE API Posted by Jun Tangunan @ 12/30/2014 1:30:04 AM
RE: Kill EXE API Posted by Mike Gagnon @ 12/30/2014 5:48:41 PM
RE: Kill EXE API Posted by Pete Sass @ 12/30/2014 6:20:59 PM
RE: Kill EXE API Posted by Victor Espina @ 12/29/2014 3:38:47 PM