Can't close Access
Posted on 2014-04-02
I hope the following will strike a chord with someone, as it is certainly puzzling me. I have Access 2010 (64-bit) running on a recent Dell server, configured as a terminal server under Server 2008 R2.
The main Access application acts as the front-end with links to tables and views on a sizeable MySQL backend. There are only about half-a-dozen users at the moment, all, like me, accessing the application via RDP, and all with their own copy of the front-end. So far, when this error has occurred I have been the only user connected (as TS Admin)
I have several other Access dbs which carry out certain processes required by the front-end at weekly intervals, one of which is giving the problem. When I run a UDF in one of the modules, which refers to a table or query (not necessarily the same one each time) the system says it can't find it, notwithstanding the table or query is definitely there, and can be opened and its contents viewed.
My inclination at that point is to stop the offending procedure, close down the module, and compact-and-repair the database. I am then advised that this cannot be done as 'another instance of the database is open'. (This despite the fact that I am the only user on the server, and have only opened this db once.) I therefore tell it to close the db, which it can't. Using 'Close' or clicking the x at the top right, either causes the current instance of Access to be refreshed, or causes a new instance to open (I'm not sure which). Anyway, it just keeps on opening Access until I reach for Task Manager and kill it. What is more, I can't kill it by closing the running application - I have to delete the process, which does close it. Incidentally, Task Manager only shows one instance of Access running.
I have been developing in Access for quite a few years and am reasonably confident the code is OK. Apart from anything else, it has been running perfectly well for weeks. Have also tried the following:
Logged off and on again
Stopped and restarted MySQL
Rebooted the server
Copied the contents of the offending database to a new version and binned the original
Rebuilt the linked MySQL views
Removed Office 2010 and loaded a completely new version
None of which made a bit of difference. If anyone has ideas, I should be very glad to hear them...