Larry Serflaten
2/22/2012 5:52:00 PM
On Feb 21, 2:42 pm, BeeJ <nos...@spamnot.com> wrote:
> I would like to perform a windows operation using a windows method
> after my VB6 app closes. The VB6 app would, as the last thing before
> unloading, start the windows "method". e.g. create then initiate a .cmd
> that has a delay at the start or some other way.
> It would be best it the Windows method would clean itself up i.e.
> delete itself but that is not mandatory.
OK, go ahead. What's stopping you? See Shell in VB help for more
info.
> I want to use something that is part of windows to do this like the
> .cmd. I know the .cmd will stick around but I could delete it the next
> time the VB6 app starts.
To do what, exactly?
> (1) What ways are there to do this?
To do what? You said your VB app will launch some task, OK, then do
it....
What other ways are you looking for, either it launches the task, or
it doesn't.
> (2) Additionally, is there a way for the VB6.exe to delete itself?
Try this: create a simple 1 form exe from VB, then run that file and
while that exe is running, try to delete it. What does Windows tell
you?
LFS