By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,493 Members | 1,179 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,493 IT Pros & Developers. It's quick & easy.

Access Shell/Instance wont quit

P: n/a
I have a VB app that has a routine that runs macros in a (password
protected) Access 97 db. (I have attached the code below.) Most of these
macros end up opening a form in the Access db for the user to interract
with.When the user finishes in the Access session they quit and are returned
to the VB app. Problem is that in many cases, when the user quits the
Access session, an Access 'shell' remains in the taskbar that cannot be
removed except by calling the task manager. This problem is compounded the
more times the user calls the macro. This seems to be some kind of bug as
it does not occur all the time. If the user clicks a button with the code
Docmd.Quit to exit the Access session, they are left with the shell. If
they instead click the x button at the top right of their screen, most of
the time the shell unloads - but not always.

Any suggestions???

PS the method of opening the password protected db for interraction is a
result of trawling user groups and is not the source of the problem as this
used to occur before the db was protected.

Dim DAODB As dao.Database
Dim objAccessApp As Access.Application

' Open DB (with password)
Set DAODB = objAccessApp.DBEngine.OpenDataBase(DBPath, False, False,
";pwd=" & DBPassword)
objAccessApp.OpenCurrentDatabase DBPath, False
DAODB.Close
Set DAODB = Nothing
objAccessApp.DoCmd.RunMacro MacroName
objAccessApp.Visible = True
objAccessApp.DoCmd.Maximize
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On Mon, 03 May 2004 08:13:03 GMT, "Andrew Chanter"
<he****@radsolutions.com.au> wrote:

Seems your problem is that the Access instance doesn't quit, which
most likely has nothing to do with how you launched it. This is a FAQ.
You should have no trouble finding help at groups.google.com.

-Tom.

I have a VB app that has a routine that runs macros in a (password
protected) Access 97 db. (I have attached the code below.) Most of these
macros end up opening a form in the Access db for the user to interract
with.When the user finishes in the Access session they quit and are returned
to the VB app. Problem is that in many cases, when the user quits the
Access session, an Access 'shell' remains in the taskbar that cannot be
removed except by calling the task manager. This problem is compounded the
more times the user calls the macro. This seems to be some kind of bug as
it does not occur all the time. If the user clicks a button with the code
Docmd.Quit to exit the Access session, they are left with the shell. If
they instead click the x button at the top right of their screen, most of
the time the shell unloads - but not always.

Any suggestions???

PS the method of opening the password protected db for interraction is a
result of trawling user groups and is not the source of the problem as this
used to occur before the db was protected.

Dim DAODB As dao.Database
Dim objAccessApp As Access.Application

' Open DB (with password)
Set DAODB = objAccessApp.DBEngine.OpenDataBase(DBPath, False, False,
";pwd=" & DBPassword)
objAccessApp.OpenCurrentDatabase DBPath, False
DAODB.Close
Set DAODB = Nothing
objAccessApp.DoCmd.RunMacro MacroName
objAccessApp.Visible = True
objAccessApp.DoCmd.Maximize


Nov 12 '05 #2

P: n/a
This is an FAQ (Frequently Asked Question)

Unfortunately it is not a WAQ (Well Answered Question.)

I have found multiple references on Google to others having similar
difficulty (mainly with Excel) but no tip that solves the problem or
explains why it happens.
I have taken on board all suggestions from the groups but to no avail. If
you can provide a link to a thread I would be appreciative.
"Tom van Stiphout" <to*****@no.spam.cox.net> wrote in message
news:rn********************************@4ax.com...
On Mon, 03 May 2004 08:13:03 GMT, "Andrew Chanter"
<he****@radsolutions.com.au> wrote:

Seems your problem is that the Access instance doesn't quit, which
most likely has nothing to do with how you launched it. This is a FAQ.
You should have no trouble finding help at groups.google.com.

-Tom.

I have a VB app that has a routine that runs macros in a (password
protected) Access 97 db. (I have attached the code below.) Most of thesemacros end up opening a form in the Access db for the user to interract
with.When the user finishes in the Access session they quit and are returnedto the VB app. Problem is that in many cases, when the user quits the
Access session, an Access 'shell' remains in the taskbar that cannot be
removed except by calling the task manager. This problem is compounded themore times the user calls the macro. This seems to be some kind of bug asit does not occur all the time. If the user clicks a button with the codeDocmd.Quit to exit the Access session, they are left with the shell. If
they instead click the x button at the top right of their screen, most of
the time the shell unloads - but not always.

Any suggestions???

PS the method of opening the password protected db for interraction is a
result of trawling user groups and is not the source of the problem as thisused to occur before the db was protected.

Dim DAODB As dao.Database
Dim objAccessApp As Access.Application

' Open DB (with password)
Set DAODB = objAccessApp.DBEngine.OpenDataBase(DBPath, False, False,
";pwd=" & DBPassword)
objAccessApp.OpenCurrentDatabase DBPath, False
DAODB.Close
Set DAODB = Nothing
objAccessApp.DoCmd.RunMacro MacroName
objAccessApp.Visible = True
objAccessApp.DoCmd.Maximize

Nov 12 '05 #3

P: n/a
On Mon, 03 May 2004 23:26:03 GMT, "Andrew Chanter"
<he****@radsolutions.com.au> wrote:

http://www.mvps.org/access/bugs/bugs0005.htm

-Tom.

This is an FAQ (Frequently Asked Question)

Unfortunately it is not a WAQ (Well Answered Question.)

I have found multiple references on Google to others having similar
difficulty (mainly with Excel) but no tip that solves the problem or
explains why it happens.
I have taken on board all suggestions from the groups but to no avail. If
you can provide a link to a thread I would be appreciative.
"Tom van Stiphout" <to*****@no.spam.cox.net> wrote in message
news:rn********************************@4ax.com.. .
On Mon, 03 May 2004 08:13:03 GMT, "Andrew Chanter"
<he****@radsolutions.com.au> wrote:

Seems your problem is that the Access instance doesn't quit, which
most likely has nothing to do with how you launched it. This is a FAQ.
You should have no trouble finding help at groups.google.com.

-Tom.

>I have a VB app that has a routine that runs macros in a (password
>protected) Access 97 db. (I have attached the code below.) Most ofthese >macros end up opening a form in the Access db for the user to interract
>with.When the user finishes in the Access session they quit and arereturned >to the VB app. Problem is that in many cases, when the user quits the
>Access session, an Access 'shell' remains in the taskbar that cannot be
>removed except by calling the task manager. This problem is compoundedthe >more times the user calls the macro. This seems to be some kind of bugas >it does not occur all the time. If the user clicks a button with thecode >Docmd.Quit to exit the Access session, they are left with the shell. If
>they instead click the x button at the top right of their screen, most of
>the time the shell unloads - but not always.
>
>Any suggestions???
>
>PS the method of opening the password protected db for interraction is a
>result of trawling user groups and is not the source of the problem asthis >used to occur before the db was protected.
>
>
>
>Dim DAODB As dao.Database
>Dim objAccessApp As Access.Application
>
>' Open DB (with password)
> Set DAODB = objAccessApp.DBEngine.OpenDataBase(DBPath, False, False,
>";pwd=" & DBPassword)
> objAccessApp.OpenCurrentDatabase DBPath, False
> DAODB.Close
> Set DAODB = Nothing
> objAccessApp.DoCmd.RunMacro MacroName
> objAccessApp.Visible = True
> objAccessApp.DoCmd.Maximize
>


Nov 12 '05 #4

P: n/a
Well at some point in the code I would have expected to see

objAccessApp.Quit
'and
Set objAccessApp = Nothing
When automating an application it is very common that the application does
not quit just because the object variable goes out of scope.

--
Terry Kreft
MVP Microsoft Access
"Andrew Chanter" <he****@radsolutions.com.au> wrote in message
news:ja***************@news-server.bigpond.net.au...
I have a VB app that has a routine that runs macros in a (password
protected) Access 97 db. (I have attached the code below.) Most of these
macros end up opening a form in the Access db for the user to interract
with.When the user finishes in the Access session they quit and are returned to the VB app. Problem is that in many cases, when the user quits the
Access session, an Access 'shell' remains in the taskbar that cannot be
removed except by calling the task manager. This problem is compounded the more times the user calls the macro. This seems to be some kind of bug as
it does not occur all the time. If the user clicks a button with the code
Docmd.Quit to exit the Access session, they are left with the shell. If
they instead click the x button at the top right of their screen, most of
the time the shell unloads - but not always.

Any suggestions???

PS the method of opening the password protected db for interraction is a
result of trawling user groups and is not the source of the problem as this used to occur before the db was protected.

Dim DAODB As dao.Database
Dim objAccessApp As Access.Application

' Open DB (with password)
Set DAODB = objAccessApp.DBEngine.OpenDataBase(DBPath, False, False,
";pwd=" & DBPassword)
objAccessApp.OpenCurrentDatabase DBPath, False
DAODB.Close
Set DAODB = Nothing
objAccessApp.DoCmd.RunMacro MacroName
objAccessApp.Visible = True
objAccessApp.DoCmd.Maximize

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.