Dear TP,
What you describe can happen in 2 instances.
1) You may actully have a network drive or linked table that is not available,
but.....
2) This same error is reported when Access can not see the code behind the form or report. So, Access thinks there must be a network error.
Why/How does this happen you ask?
With Access 2000 and later versions, if you import a form, report or module or
If you copy and paste one of these objects or
If you rename one of these objects,
You MUST open up a code window and compile the code. This completes the access copy/import/rename process.
If you do not compile the database, then you may see the error you report.
To fix this, try again by creating a blank database, import all objects and then, first thing, open up a code window and compile the database. You must get a clean database compile.
Once this happens, make a backup.
If this suggestion does not work, then you must import your forms and reports, one at a time and compile. Whatever compiles good, that is a good thing, but whatever still will not work must be imported from an older backup or must be written from scratch.
Remember:
1) Backup often
2) When you copy or past or import a form, module or report, the next step should always be to compile
3) backup, Backup, Bacakup.
Good Luck,
Hap...
Access Developer
Access based Add-on Solutions
Access Consultants forum