473,326 Members | 2,114 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,326 software developers and data experts.

Access Shell/Instance wont quit

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
4 2606
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
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
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
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 thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

1
by: David Conorozzo | last post by:
I create a new Access.Application instance. As soon as I refernce the property "References", I am unable to issue a truly successful quit on that instance. By that I mean the call to quit is fine...
41
by: Ruby Tuesday | last post by:
Hi, I was wondering if expert can give me some lite to convert my word table into access database. Note: within each cell of my word table(s), some has multi-line data in it. In addition, there...
4
by: Lauren Quantrell | last post by:
If an Access2K ade is running, say it's named app1.ade, and I open app2.ade, I want app2.ade to determine if app1.ade is running, and if it is, I want app2.ade to close app1.ade. Is this easy? lq
4
by: Andrew Chanter | last post by:
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...
15
by: Mark C | last post by:
All, I have exhaustingly been looking through the newsgroups in search of a way to systemically output an Access 97 report to a pdf file using the full version of Adobe Acrobat. I want the user...
1
by: David | last post by:
Does anyone know how to run MS Access reports from VB.net. I'd like to keep the existing reports in the database if I can. Thanks David
3
by: Tony A. | last post by:
I'm in the process of migrating a MS Access 2003 application to VB .Net (2005). How can I run the reports in Access from the VB application? -- Tony
16
by: JoeW | last post by:
I'm utilizing a database that I created within MS Access within a program I've created in VB.NET. I am using the VB front end to navigate the information, but want to be able to print a report,...
7
by: farhaaad | last post by:
Hi everybody, I just wanted to know if i can make a form in excel (the same as access forms), so when i enter data in excel form it goes to a table in access ? I mean when i enter a value in a...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.