Error accessing file. Network connection may have been lost (1 Viewer)

I think the damage to my database is not recoverable, but i'm still hoping.
My computer crashed when I was working on my dtabase and after restart the db is not working anymore If I try to do something, anything (!!!) all I got is an error message: "Error accessing file. Network connection may have been lost." But the db is on my computer, I don't use it over the network.
What can I do to make it working again?
Thanx!

Attila

Before you do anything, make a copy of it!

Try importing all db objects into a NEW database.

Huhhhhh!

Oh, God! I was so scared! I tried to export it to a blank database, but it gaved me some errors, i think on the form wich were opened when the crash occured. After exporting, same errors.
Now, following your advice, I exported again, but without selecting those forms wich were opened, and it's working!!!!!!!!!!!!!! Oh, I was so scared, I'm working on this db from 2-3 weeks, I was afraid that I lost everything.
Thank you, thank you, Ghudson, now I can have a happy weekend!
All my respects.

Attila

Oh, noooooooooooo

I was rushed in conclusions! It was working, but after setting the startup form, closing and opened it again, it happened the same. The same error message.
What else could I do?

Thanx
Attila

Not sure about the error message you are getting but you can check out this link for a possible solution.

How-to articles - Corrupted or Damaged File

Sample code to import all database objects in Access

In the past we have this same problem with certain DB's. What we ended up doing to resolve the issue orginally was move the DB to a different server on a different network segment, and after our network upgrade it became a non-issue. We found with Access (version 2K and less in our case since the upgrade on the network, so can't speak about higher versions) any kind of little network glitch seemed to cause this problem. Things that did not seem to effect any other systems. And of course the network folks said it was the application. We stumbled upon the different network segment by accident, without compacting/fixing the DB. It was like night and day for us.
Now I am not saying this is your problem mind you, you could test this my moving everything local and giving it a good shake down (but on one hand you don';t the usage that way). But I wish to mention it just in case. I am not sure about the specifics behind the error (at least in ouor case) since it has been a few years. But it only happened on Access applications using Access DB's (FE/BE or all in one). VB and Web apps using Access did not seem to be effected with the same issues.

I have just succeeded in a very frustrating battle with this same problem; in my case it arose from using the import/export feature, moving from one access db to another; found info on another thread here, it is a recognized problem on Access 2k that is solved by doing an upgrade to SP3. see this link: http://support.microsoft.com/default.aspx?scid=kb;en-us;304548

worked for me, good luck!

Happy

Thank you, guys!

I have copied my database to another computer, I have created a blanc database on that computer and imported all database object into this new database. Now everything looks normal. I have tested it, and it's working normally.
Thanks again, you are great guys!

Attila

woo! back in action!

seshima said:

I have just succeeded in a very frustrating battle with this same problem; in my case it arose from using the import/export feature, moving from one access db to another; found info on another thread here, it is a recognized problem on Access 2k that is solved by doing an upgrade to SP3. see this link: http://support.microsoft.com/default.aspx?scid=kb;en-us;304548

worked for me, good luck!

Click to expand...

Thank you so much for the tip, seshima. Thanks to you I had sufficient reason for IT to upgrade me from Office 2000 to 2003, hehe... Of course, this caused a whole other set of issues trying to upgrade (is everyone's IT dept like this? lol), but I think we've got most of the kinks worked out and it seems like my new database is functioning just fine now - no more funky errors! Thanks a ton.