[AccessD] Orphaned program instances

Thanks, always good advice.  The client is not too religious about
installing service packs.

John W. Colby
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Darren DICK
Sent: Monday, May 24, 2004 9:15 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Orphaned program instances


HI John
I am not 100%  if this is the same thing.
I had an installed Access app on a clients XP machine
Each time they would open a the app then navigate to a particular form that
had a sub form in it
nothing visible would happen. But when they would close the app (And Access
of course)
and want to start (double-click the icon) the app again there would be
strange behaviours.
IE the app would fail at one level or another. I would shut down that
instance of access and the hit
CTL+ALT+DELETE. That would show up the errant (orphaned) foot print of
msaccess.exe - still running
in the processes list.Even though there were none visible (task bar or
visible apps)
It would have to be stopped from the Processes Window - no other way

I tried to code and recode around this for ages - no success Both I and the
client just put up with it.
Then just last week he agreed it was his computer causing these errant
(orphaned) footprints because
the same thing had happened to him whilst he was in Word - IE a Word
footprint was left 'running' after closing
Word - Of course you can only see this in the processes of Task Manager.

So...Installed the Latest Office Service pack and now all is well.
This had pi**ed me off for about 5 months and the customer put up with it
(thankfully)
So if you are having the same problems try the latest Office Service Pack
for your version.

Not very technical but it fixed it.

See ya

DD



----- Original Message -----
From: "John W. Colby" <jwcolby at colbyconsulting.com>
To: "AccessD" <AccessD at databaseadvisors.com>
Sent: Tuesday, May 25, 2004 10:32 AM
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
--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com