"Can't exit Access now" error

[skydiver]

Access 2010. I've created a database on my thumbdrive and I'm now wishing to place it on our network for multi-users. In copying/pasting the database the the network drive I'm getting the following error message when either trying to Compact and Repair and/or just simply close the darn thing.

Error message:

You can't exit the Microsoft Access now.

If you're running a Visual Basic module that is using OLE or DDE, you may need to interrupt the moduel.

 

[boblarson]

1. Your database should be split (backend tables only and frontend everything else).

2. Your frontend should be a copy on EACH USER'S COMPUTER.

Failure to follow those rules will potentially result in corruption.

See here for more about that.


As for the Can't Exit Access Now, normally that is some VBA running which requires the database to be open. You don't have any code in the close event of a form or something do you?

 

[skydiver]

You're scaring me Bob! What type of corruption are you talking about? I believe you meant to include a hyperlink perhaps, to further review splitting a database, but I don't see anything. Regarding our shared network...there will be 2 people inputting data and 3-4 people running reports off the same shared drive. Does this make a difference? We've been using the old database (2003) for 2-1/2 years with no issues. I've revamped the new database (2010) using basically the same format/structure. Should I be worried? Thanks Bob!

 

[skydiver]

Oh, the thing about the error message I was getting...it had something to do with a macro I had on Unloading the switchboard form (QuitAccess). I removed the macro and the error stopped. Why can't I use this macro?

 

[skydiver]

Sorry for the the various postings here. One more clarification regarding the splitting of THIS database. In my previous post, I mentioned 2 people would be inputting and 3-4 running reports. Since our office is very small the 2 people inputting will always be inputting at different times...never at the same time. So, with that said...is a split necessary under these circumstances??? Thank you!!!

 

[boblarson]

So, with that said...is a split necessary under these circumstances??? Thank you!!!

Yes, even if only ONE person is using it, it is smart to split. And here's the link I forgot to include in my last post:
http://www.kallal.ca/Articles/split/index.htm

And, as far as the macro goes, what was the macro supposed to do?

 

[skydiver]

I wil review your link about splitting the database. Regarding the macro...on Unload, I set it to "QuitAcess." Without it...the database closes, but Access remains open so I have to Exit the application. It's no big deal, but it would be nice to hit the "Exit" command button on my switchboard form and close the database AND Access entirely.

 

[boblarson]

Change your switchboard button to not close database but create your own function to do so in a standard module

Function CloseAccessApp()
    Application.Quit
End Function

And then in your switchboard item select RUN CODE and put in CloseAccessApp() as the argument.