Vista - How can I manage/encapsulate failures of an Active X control

I have an Active-X control provided by a vendor that will inadvertenly
crash while processing. The good part is that I do have a way to save
information routinely as it is processing in the event it crashes.
From there I can start over and I can eventually finish the process.

My problem is that at this stage I have been doing this manually, but
now I have to come up with an automated solution. What I want is to
have my program run, save the data at increments and restart when the
Active- X control crashed without the user ever knowing it.

My mayor concern which is also the main question. Is how to do it the
best way, and if there is a possibility for memory leaks.? The problem
with a memory leak is that eventually the spawning process may not
work and it would default to the original behaviour of crashing in the
middle of the process. I would normally want to call the process using
a regular procedure call instead of a command line call. But it may be
that the command line islates the processes better.

I am asigning "Nothing" to the Active-X object at the end of the run,
and I also have a try block to make sure the asignment runs.


Thanks in advance for any help.

Arturo Hernandez

I have an Active-X control provided by a vendor that will
inadvertenly
crash while processing. The good part is that I do have a way to save
information routinely as it is processing in the event it crashes.
From there I can start over and I can eventually finish the process.

My problem is that at this stage I have been doing this manually, but
now I have to come up with an automated solution. What I want is to
have my program run, save the data at increments and restart when the
Active- X control crashed without the user ever knowing it.

My mayor concern which is also the main question. Is how to do it the
best way, and if there is a possibility for memory leaks.? The
problem
with a memory leak is that eventually the spawning process may not
work and it would default to the original behaviour of crashing in
the
middle of the process. I would normally want to call the process
using
a regular procedure call instead of a command line call. But it may
be
that the command line islates the processes better.

I am asigning "Nothing" to the Active-X object at the end of the run,
and I also have a try block to make sure the asignment runs.

Thanks in advance for any help.

Arturo Hernandez