Re: VB / DLL Issues
- From: "Ken Halter" <Ken_Halter@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 4 Oct 2006 18:21:59 -0700
<stumorgan@xxxxxxxxx> wrote in message
news:1159990826.612123.252930@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
If you have any other ideas I'd be very very happy, this has been
plaguing me for 2 days now.
Thanks,
Stu
If there are any controls on that form, the form's Got/LostFocus will never
fire so... have you checked the Activate/Deactivate events? Even those won't
fire when switching apps.
Does that driver do something to a control on your form directly? I've heard
of some drivers writing output to a textbox but I've never used any of them.
So, if minimizing fixes the problem, I assume unloading and reloading fixes
things too?
If that's the case, you might try creating a 'wrapper' class to interact
with that driver. After calling the driver's Kill method, destroy the class
and watch for its Terminate event to fire (place a couple of Debug.Prints in
there). If Terminate fires, the next time you create an instance of the
class, you should be back at "square one" as far as the driver's concerned.
Using a class will also eliminate the need to unload/reload the form.
--
Ken Halter - Please keep all discussions in the groups..
In Loving Memory - http://www.vbsight.com/Remembrance.htm
.
- Follow-Ups:
- Re: VB / DLL Issues
- From: stumorgan
- Re: VB / DLL Issues
- References:
- VB / DLL Issues
- From: stumorgan
- VB / DLL Issues
- Prev by Date: Re: Trying to be 'well behaved' under Vista
- Next by Date: Re: Custom class know what class owns it
- Previous by thread: VB / DLL Issues
- Next by thread: Re: VB / DLL Issues
- Index(es):
Relevant Pages
|