msaccess.exe running in the background

[Gordon Prince]

I've got an Access 2000 application that uses Outlook 2002 extensively without any problems. I've added some VBscript to a couple of custom Outlook 2002 forms that seems to create extra copies of msaccess.exe running in the background. Once these get going, my VBscript doesn't work properly. I'm trying to figure out how to trouble shoot this problem.

The symptom is that the VBscript in the Outlook form works several times for the user, then when the user clicks on it, nothing happens. If the user closes Outlook + Access, there's still an msaccess.exe running (as seen with the Task Manager). The only way to get the VBscript working again is to kill the extra msaccess.exe process.

I can't figure out where the extra msaccess.exe is coming from. I've been through all the VBscript and every place there's an access object used, I set it back to nothing. E.g.
Set appAccess = GetObject(, "Access.Application")

appAccess.run "OutlookShowMatter", dblMatNo

set appAccess = nothing

I can't think of what else to do to stop these msaccess.exe tasks from getting started. Any ideas?

 

[Cheryl Fischer]

Gordon,

According to the article by Dev Ashish and Michael Kaplan:

Automation Object Does Not Close Automatically
http://www.mvps.org/access/general/gen0017.htm

setting an Object to Nothing does not close it. This is an excellent
article with code samples that you can adapt for your use.

hth,
--
Cheryl Fischer
Law/Sys Associates
Houston, TX

I've got an Access 2000 application that uses Outlook 2002 extensively
without any problems. I've added some VBscript to a couple of custom Outlook
2002 forms that seems to create extra copies of msaccess.exe running in the
background. Once these get going, my VBscript doesn't work properly. I'm
trying to figure out how to trouble shoot this problem.

The symptom is that the VBscript in the Outlook form works several times for
the user, then when the user clicks on it, nothing happens. If the user
closes Outlook + Access, there's still an msaccess.exe running (as seen with
the Task Manager). The only way to get the VBscript working again is to kill
the extra msaccess.exe process.

I can't figure out where the extra msaccess.exe is coming from. I've been
through all the VBscript and every place there's an access object used, I
set it back to nothing. E.g.
Set appAccess = GetObject(, "Access.Application")
appAccess.run "OutlookShowMatter", dblMatNo
set appAccess = nothing
I can't think of what else to do to stop these msaccess.exe tasks from
getting started. Any ideas?

 

[Gordon Prince, MCP]

Thanks for the ideas.