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

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

Regardless of what the error message says, you can also get this error for a database on a local drive. In such instance the error is due to the inability of Access to write to the drive. To remedy the situation, do the following:-

1. Ensure the drive on which the database is situated is not write-protected.
2. Ensure you can create a file and delete in the location where the database is situated.
3. Run Windows disk scanner to remove read/write errors. Read/write errors can occur if your system hangs due to a hardware fault and you had to restart the computer.

Hopes this helps.

Thanks

Bindi Gill

Malaysia

The IT department I consult with reported the same problem as migration to Windows 7 and Office 2010 is underway (from XP and Access 2007). They also use a Citrix server for national support.

The problem is only on Window 7, not on XP.

I sent the SMB 2.0 patch code from MSDN that will also show the same error. They ran that and it did not change anything.

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_25594983.html

this is a subscription site. I have yet to get an account. But, they claim to have tried seveal things with out success (listed at this link).

Just a note: Upgraded Access 2000 to Access 2007. Front end - linked to back end. No problems with this for last year, until Windows 7 - Office 2010 roll out. Had tested compatibility on a stand-alone workstation of Wondows 7 / Office 2010 (C: / drive) to validate code, DLL, and Excel reporting automation. No problems found.

I find rebooting doesn't particularly help - often I get this message when i just turn on my computer and go straight into the database. Could it be related to using the database with the back-end links to a mapped drive instead of full network path? has anyone tried recreating al their links using the full network path instead of the mapped drive name? I notice if you run as administrator (or via task scheduler in win 7) then you can't use mapped names at all, you have to put in the full paths.

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?

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/