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

App won't close

P: n/a
A few months ago, a working Access97 system started exhibiting this behavior. About half the time when the .mde is closed, the app window remains open and can then only be closed by using "End task" from Task Manager, or sometimes a right click "Close" will work on the button on the Task Bar (but only on W2K stations, as opposed to NT stations, I think).
Ideas?

--
Message posted via http://www.accessmonster.com
Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
James Birkholz via AccessMonster.com wrote:
A few months ago, a working Access97 system started exhibiting this behavior. About half the time when the .mde is closed, the app window remains open and can then only be closed by using "End task" from Task Manager, or sometimes a right click "Close" will work on the button on the Task Bar (but only on W2K stations, as opposed to NT stations, I think).
Ideas?

Did you modify the code or make any changes in the MDE?
Nov 13 '05 #2

P: n/a
Yes,it's under constant developement, with the users running fresh copies as .mde's. However, I have no idea what had been changed at the point this started, it took a week or so for it come to my attention, and even longer for it become an issue. I had hoped that like similar weird things that often happen with Access, it would eventually go away. So I was just hoping that it wasn't so rare that someone else might have already been down this road and have some ideas where to start looking. It's still just an annoyance, so I can't justify spending days trying to track down the source.

--
Message posted via http://www.accessmonster.com
Nov 13 '05 #3

P: n/a
James Birkholz via AccessMonster.com wrote:
Yes,it's under constant developement, with the users running fresh copies as .mde's. However, I have no idea what had been changed at the point this started, it took a week or so for it come to my attention, and even longer for it become an issue. I had hoped that like similar weird things that often happen with Access, it would eventually go away. So I was just hoping that it wasn't so rare that someone else might have already been down this road and have some ideas where to start looking. It's still just an annoyance, so I can't justify spending days trying to track down the source.


I had this happen occasionally in A97. The best thing I could advise is
making sure all the DAO objects you open you close and set to nothing:

'close recordset and set to nothing

rst.close
set rst = nothing

'same for any queries

qdf1.close
set qdf1 = nothing

'database

dbs.close
set dbs = nothing

The best way to do this, of course is to make sure your procs ALL have
one and only one exit point. Don't have any if statements like:

IF <blah blah> then exit sub/function

Rather have a labelled exit point:

Exit_Proc:

rst.close
set rst = nothing

qdf1.close
set qdf1 = nothing

dbs.close
set dbs = nothing

Exit sub/function

And your if statement can be:

IF <blah blah> then goto exit_proc

Similarly, your error handling section should also have goto Exit_proc

I found when I was disciplined with this sort of approach, the problem
you descibe went away.

--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
Nov 13 '05 #4

P: n/a
Thanks, I'll start with those leads!

--
Message posted via http://www.accessmonster.com
Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.