[AccessD] Orphaned program instances

I have ran into the same problem...I believe it is a timing issue. If you
get ahead of the document processing, the instance of Word does not close
even though you have apparently exited properly. I do not have the code here
but I believe I resolved it by running a DoEvent with a 'borrow' piece of
API sample code, from Leban's web site that watched for instances of Word
and a global variable. (Now that I have given you such an accurate
description, the rest should be easy....<grin>)

HTH
Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John W. Colby
Sent: Monday, May 24, 2004 5:32 PM
To: AccessD
Subject: [AccessD] Orphaned program instances


I am doing mail merge and have times when instances of Word get "orphaned",
i.e. are loaded but not visible on the task bar.  This prevents the next
merge cycle.  I don't think that I am causing the orphans, they don't happen
often but they are occurring.  I don't know how to troubleshoot what is
causing them, how they were opened etc.

Is there any way to get a handle to these instances and close them
programmatically?

John W. Colby
www.ColbyConsulting.com


--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com