File not found error

[OzNet]

The database I have been working on has now starting producing this error.

Each time I try to edit a vba code it produces this error. I can't even put in the comment symbol in to comment out lines of code.

What is even more puzzling is that it occurs regardless of any form I open the try to edit code.

I have been playing around with queries trying to achieve a certain result but this would have no bearing on some of the forms I now open and can't edit their code.

I wondered if a dll file had become corrupted but when I open the Northwind db I can edit code ok.

I am not sure what to do. Any suggestion would be helpful.

Many thanks

[Delerna]

Have you tried creating a new database and importing all the objects from the old into the new. Maybe the database file is corrupt?
I haven't encountered your scenario before so this is just a stab in the dark !!!

[OzNet]

Thanks Delerna

This is what I have done.

I made a copy of the db and progressively deleted forms and queries until I only had all the table and one form and query left. It was still producing the error.

I had thought of trying your suggestion of creating a new db and importing the components into it but I found a backup copy that was behaving itself, so this won't be necessary.

As I think about it, a couple of times the access programme (access 2007) mucked up and automatically created backup files. However, everything thing seemed to continue afterwards ok. When I checked these backups, some produced the error, one did not have any vba code in it and one was nearly the same as before the melt down. I have duplicated this copy and will continue my work.

I still don't know what the cause is - it is almost like the code module has been deleted yet I can still see the code. Certainly, something has been corrupted and fortunately I found a backup that I can work with.

[Arble]

I had this problem this morning. The application ran without problem the night before, but gave the error as you described it. I deleted a module that was completely commented out, and the problem immediately went away. Can't explain why.