File Not Found

[TOPSie]

I write this mainly as a guide to others, but also in the hope that someone has a better answer.
I maintain a very large accdb/mdb application. I use Access 2016 (Windows 10) on a development machine and deploy updated versions to 2 production PCs on a regular basis.
Whenever I make changes I do it in very small steps and create numbered versions for each small change (I am currently up to version 658)

Occasionally (far more often than I would like) the latest version will throw the "File Not Found" error and the version is unusable.


So I mark the latest version as "Duff" and regress to the previous working version and then reapply the changes (code and or design) and call it "latest version Mark2" and it works!!!

Each time this happens I try without success to diagnose the error. Sometimes the Debug/Compile shows a compilation error - mostly it doesn't. I have found nothing else and certainly no indication of which File is missing.
Even more worrying is that sometimes the code on the development PC works fine, but when deployed to a production PC (in exactly the same way as ever) the production PC throws File Not Found. Again the regress/reapply changes (on the development PC and redeploy fixes it.
One minor clue is that it seems to happen if whilst creating the new version I have used debug and stepped through the new code (or old code) looking for an issue. I always remove the break points before deployment but perhaps some remnant of the debugging is left behind (just a theory which I can't prove)

So the answer is baby steps and keep a careful records of changes at every (small) step and be prepared to regress/reapply.

[Minty]

Have you decompiled and recompiled?
Guide here: http://www.fmsinc.com/MicrosoftAcces.../Decompile.asp, or alternatively (and possibly better) imported all the objects into a fresh new database?

It sounds like you have some underlying corruption somewhere, and it can be very difficult to track down.

[Micron]

You shouldn't be having that problem, and fixing that would be better than managing it on an on-going basis. Some thoughts:
- decompile then recompile as suggested
- it seems you don't know what file is being referred to in the error. If the fe opens then it may be the be. Try refreshing the links.
- does code run (by autoexec or default opening form) and does it refer to a file in any way? Auto loading form may be corrupt.
- you say sometimes you get a compile error. Where? If in a form module but you can't see what causes the error, that form or a control on it may be corrupt.
- production pc's are using Access Runtime or full version?
- which one experiences failure? If only 1, perhaps Office/Access repair or re-install. If both pc's, likely not the problem but couldn't hurt.
- I've reviewed your post and cannot tell if the fe actually opens. Additional code may help to pinpoint or prevent the error, such as testing for be connection assuming fe opens.
- if error occurs when user clicks icon to open db, then it is the fe that cannot be found? That doesn't seem plausible based on your post though.
- you do not have either file in any folder synced to One Drive I hope. Certainly, fe or be is not being Accessed from OD directly?
- how do you edit design? If you modify last copy only and it is faulty, the fault remains. Did you ever open fresh db and import everything into it from prior version. If an object is corrupt, you'd bring that over so it likely would not solve anything. However, if the base db is corrupt, you should be able to get rid of that by starting fresh and importing objects.
That's all I can think of for now.

[Gicu]

Some more reading for you:
https://stackoverflow.com/questions/...in-access-2007

Cheers,

[TOPSie]

Some more reading for you:
https://stackoverflow.com/questions/...in-access-2007

Thanks to everyone who has responded, it has been a very useful read through all the suggestions.
I tried the decompile, recompile, compress route several times - it seems that decompile doesn't like a linked database on a different drive ( my mdb is on a server mapped to the N: drive)
So I unlinked and did the business before relinking.
However it did not work.

In truth this particular incarnation of the issue was not actually "File Not Found", everything worked on my development machine, but on a production machine the app simply disappeared with no error message of any sort shortly after starting.

I tried many combinations - but the only thing which worked was to regress 2 versions.

Browsing through the link above there are several references to the autostart module (start up form) and simply making a minor change (e.g. add a blank line to the code). In my case I deleted 2 blank lines.Saved everything and uploaded this version to production. All now works???

So in this case decompile does not fix it but a minor change (and hence a recompile of the autostart form) seems to fix whatever issue was causing the problem

Once again thanks to everyone - for those in the UK enjoy the Bank Holiday

[Welshgasman]

Well done. I would have never thought of deleting blank lines, as I like to use those for code clarity.

[isladogs]

Sometimes Access apps develop 'phantom break points' e.g. if the app is closed whilst one or more break points are in place.
When the code is run again, it may stop at the 'phantom break' or possibly throw a compile error such as File Not Found
Making a minor code change or adding/deleting a blank line will indeed force a recompile and often avoid the issue

[Micron]

AFAIK it is possible that even after compiling, the compiled version of the code can be different from what you're reading, and it can drive you nuts trying to find what's wrong. However, a decompile is supposed to fix that. I have edited code and then removed the changes just to force the ability to compile again, but I've never removed lines to fix a problem that went away without compiling again.