I tried all the above solutions an they all fixed the problem, only to have the problem reappear sometime later - always after VBA code change. I have had this problem for years in my access database. Now, a few days later I have de-compiled, compacted and re-compiled the database, halving its size, so maybe that will have done the trick. There is no one obvious module involved, although I will probably suspect the form module I have been working on most recently if the problem persists in a troublesome way. 'Debug, Compile' is possible and doesn't suggest any problem.įor me too, typing one space (or blank line or other character) anywhere in the code, and then deleting it, and saving, closing and re-opening seemed to provide a workaround, and all has been well for the last few days (I am the only user at present). On opening the database it says 'File Not Found' and throws up a public module (not one on which I have been working extensively recently), without opening the Autoexec (Switchboard) form. My DBs too have been through several versions of Access.
mdb front ends running in Access 2013, after the August 2019 update to Windows 10. Hope this observation may spare many unnecessary un-/re-installations of Office and other desperate attempts.Ī similar thing has just happened to me a couple of times with one of my. (I'll make a note of this thread to add new insights once I worked with this file again in PowerPoint 2016.) This being said, I wonder if PowerPoint 2016 saving is peculiar and if I can replicate/if I will run into the error again if saving the file again in PowerPoint 2016 and returning to PowerPoint 2010. After this re-saving in PowerPoint 2013, the file seems to work fine again in PowerPoint 2010 und did not show any problems after the first few edits, saves and re-opening. I compiled the VBA project to check for error.
As I could start PowerPoint 2013 more easily (virtual machine) than PowerPoint 2016 (different Windows 10 boot partition), I tried to open the troubled file in PowerPoint 2013 and had no problems. Started to do a quick search on the internet and found only "shooting in the dark" suggestions. So I've got the idea of some file in the. pptm but I had no startup procedure involving a file. (Reminded me of another nasty error VBA sometimes shows on startup for no obious reason and erratically.) Luckily this error started after my first edits in PowerPoint 2010 after having tested the file in PowerPoint 2016. Weird also that the error message does not give a file name for the file not found. Though programming VBA for years now, I had never had an unsolicited "File not found:" error. This error "File not found:" may be caused by differing save behavior of Office versions and may not have anything to do with your code! In case of this error, try to open and save your troubled file in another Office version and it may work fine back in your main Office version.
Though this thread is over a year old I would like to share another very helpful observation. What's the problem? Is the database somehow partially corrupted? What should I do? This is really annoying. Half the time and users can't do much they need to restart the database once or twice to get it back working, and after a few minutes the error might happen again.īecause this is Access 2007 and there are a lot of people experiencing this bug, I can't believe it isn't more documented. My database can be okay for a week and then the problem starts to happen again. There are other examples too, with no real solutions yet. It's like a compilation error but it's only happening 5-10% of the time, which is really weird.Īfter some research, I found other people are having the same problem, for example this and this link. I tried adding the Stop command at the beginning of the executed block to try debugging it, but no code is executed at all.
When this happens the only thing to do is to restart the database. For example, without any specific reason, clicking on a button or trying to execute any code will return the error: Recently, some users have started to experience problems with the buttons in my forms. I'm working on a big Access 2003 project with Microsoft Access 2007.