Can't get MS Access to quit

[Poobear1929]

Hi, I am having a devil of a time trying to get MS Access to quit. I have an Access application that uses a work group file for the security, I don't think that is the cause but I just want to throw that out there. Anyway, when I go to exit the database appears to close, but then an empty Access window opens back up. I keep going to exit, but it just keeps popping back up. I end up having to cnrtl alt delete and stop Access altogether. I just can't figure out what the problem is.

Anyone have this problem before?

Thanks

 

[JBinQLD]

g'day poo,

never heard of that so i'd guess it's machine specific? If it's happening on all machines then perhaps something funcky in logic of quit button? Compact and repair? Certainly a weirdo sounding problem.

If it's machine specific which is my suspicion, try reinstalling access, then windows. yey! The joy of being bonded to MicroSoft, surely the worlds most love-to-hate compny ever!

JB

Oh, you should prolly hold off dong something radical cos many of the guys on here put my experience to shame despite my years. reinsstalling windows is possibly a bit gung-ho..

 

[PHV]

Perhaps you have checked the 'Compact on close' option ?

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[Poobear1929]

Thanks guys, but I inherited this problem. All users no matter what version of Office or Windows they have, all have this same problem.

I run Windows XP and Office 2003 and my users use Windows 2000 and Office 2000. It is the strangest thing. I have tried a button that tells the application to quit, it seems to work for a few seconds then Access pops back up and it is an empty window. I will go up to the file menu and hit exit and nothing. It appears to close that instance of Access, but a new one just pops back up and it is empty. Compacting and repairing has not fixed the problem. My users have learned to just live with it, but I am trying to figure out what is going on.

I thought it may have to do with the workgroup. See the Access application this happen with is broken down into 5 databases. I will click on my shortcut with will ask for my login, then I have pointed the shortcut to the most used database. If I need to go to another one using the same workgroup, then I just close that database and through the same instance of Access that I opened up through I go to file and open. Then I browse to the new database that I want to work in. This is so the user doesn't have to relogin each time. Anyway, I didn't design this mess, I a just inherited it. So I don't know if there maybe something screwy with how we have to navigate through the different databases that make up the whole Access Application that we are using. Now just to throw this out there, I don't have this issue with other Access projects.
Thanks,
Poo

 

[dhookom]

I would check for a hidden form with code in the On Close event that cancels the closing. This might also be an issue with not closing a recordset or other object reference.

In an earlier version of Access, if you had a check box on a subform and referenced it in code this might happen. I have a short explaination and sample MDB at Check Box Test.


Duane
Hook'D on Access
MS Access MVP

 

[Hap007]

Dear PooBear,

I experienced similar problems with an MS Access program several years back.

My research at that time uncovered a problem, where if you used a recordset in VBA code and you failed to close the recordset and db, then sometimes MS Access would not close. You would just wind up with an Empty Access Window hanging around.

My experience shows that many programmers fail to close the recordset and db at the end of the module and it works just fine, but this was a documented problem and solution on the MSDN web site several years back.

If you have coded many 'open db and recordsets', in functions or subroutines, and did not close the recordsets, then it might be tough to find the one that is causing you issues.

I might suggest adding 'close' logic in all functions and subroutines that you have created.

Second suggestion, just start your application and run just one form or report and then exit. Do this until you find which module is causing you problems, and code the close for that recordset.

Hope This Helps,
Hap...

Access Developer

http://www.fcs-software.com/fcsaccessdev.html

Access based Accounting Solutions - with free source code
Access Consultants forum

http://www.tek-tips.com/threadminder.cfm?pid=1121

 

[Poobear1929]

Thanks Hap,

I am afraid you maybe right. I didn't develop this crazy application, but I do know how important it is to close recordsets. When I have time, I will have to go through the whole thing and try to isolate where the problem is. I hate having to fix other people mistakes.

Thanks again for the info.

Poo