SOLUTION TO ERROR " Your network access was interrupted. To continue close the database and then open it again." __

You also need to be careful using a flash drive in this manner. I've seen beaucoup reports over the past few years about data corruption in Access when using a flash drive in this manner. Apparently many flash drives report that data transfer is complete when, in fact, it isn't quite, and disconnecting before the transfer is complete is apt to cause corruption.

Linq ;0)>

There's always more than one way to skin a cat!

PaganLinq wrote in

news:*** Email address is removed for privacy ***

m:

You also need to be careful using a flash drive in this manner.

I've seen beaucoup reports over the past few years about data

corruption in Access when using a flash drive in this manner.

Apparently many flash drives report that data transfer is complete

when, in fact, it isn't quite, and disconnecting before the

transfer is complete is apt to cause corruption.

That is going to happen only if you pull the Flash drive without

using the SAFELY REMOVE HARDWARE icon in the notification area. If

you do it the right way, you'll never lose data.

But I know from experience that most people don't have a frigging

clue about this and just pull the things when they feel like it.

David W. Fenton                  http://www.dfenton.com/ contact via website only     http://www.dfenton.com/DFA/

I have an user with Windows XP SP3 / Access 2010 version 14.0.5128.5000 (32-bit) who got this error message today while using a database on a mapped server drive.

He uses this database every day and this is the first time he has received the error message. His laptop is docked - i.e. network cable hard wired - so there should not be an issue with his connection to the mapped server drive.

After we ran the Compact & Repair function, the user reported a table and several queries were missing, which we were able to restore from a backup copy of the database.

This is the first time we have encountered this error message so I am just looking for information and possible causes/resolutions.

I just experienced this problem for the first time.  I keep a dev copy of my database on my local drive, make all my changes to it, then copy it to the production network drive.  Before I overwrite the existing production database, I make a copy in an archive folder. 

While exiting my dev copy, I had a problem and MS Access crashed, so I reopened the dev database and it seemed fine, all my forms and reports worked.  I then copied it to the hard drive and gave it the "prod" name.  I tried running the "prod" version, and received the above mentioned error message. 

I then reopened my dev copy, ran "compact and repair database", recopied it to prod, renamed it, and STILL got the same message. 

I then asked another user to open the prod version, and he could open the "prod" version without a problem.  I was doing this successfully as recent as two weeks ago without a problem.  I have not updated or changed my laptop. 

I find it odd that it works okay locally, and when copied to the network and renamed, works for someone else, but not me,   Any suggestions?

This is such a nuisance behavior. Searching online doesn’t show any solutions.

Does rebooting help?