Hi

Scenario is project is split FE/BE, where both FE and BE are on the C drive of the same machine. Directories are

FE - C:\AMP\AMP.accdb

and

BE - C:\AMP\Data\AMPData.accdb

Machine details are Vista Ultimate 32 bit, Access 2007. OS and Access both fully pathched. No mapped network drives.

Now the headscratcher -

Linking to the tables using the standard C:\AMP\Data\AMPData.accdb works fine, but using the UNC version of \\PCName\AMP\Data\AMPData.accdb fails with the error message

Your network access was interrupted. To continue, close the database, and then reopen it again

I can link to the BE from other PC's across the network with no problems, just not from the PC that the back end actually resides on unless I use C:\AMP\Data\AMPData.accdb as the path and not \\PCName\AMP\Data\AMPData.accdb

The issue has only just started happening, and to the best of my knowledge there's been no changes made to the PC, well I guess obviously there has but certainly not by me and no-one else has access to this machine.

Whilst testing things, from the Immediate Window if I try

?Len(Dir("C:\AMP\AMP.accdb"))

I get the correct result, but using

?Len(Dir("\\PCName\AMP\AMP.accdb"))

produces Runtime error 52 Bad file name or number

It clearly can't be a network error as linking to the tables from a different PC across the network works fine, it only occurs when using the machine that the BE is actually on.

Google/Bing searches produces lots of results with others having the same error and the odd one or two suggestions but no solutions that I've found so far. Any suggestions or insights will be very gratefully received

Hi Alan,

As far as I know, the UNC syntax requires the device name and share name. Try the following:

?Len(Dir("\\PCName\C$\AMP\AMP.accdb"))

Just my 2 cents... (IMG:style_emoticons/default/2cents.gif)

Hi DBG

Thanks for the suggestion, but same result (Runtime error 52 Bad file name or number)

I only tried things in the Immediate Window for testing purposes, it's the linked table path that's stored in the Database field of the MSysObjects table that's causing me the issue and the "Your network access was interrupted. To continue, close the database, and then reopen it again" error

To be specific, at the moment the path stored in the table (MSysObjects) is currently C:\AMP\Data\AMPData.accdb which works with no problems. If, however, that's changed to \\PCName\AMP\Data\AMPData.accdb as it would normally be for a UNC path, I get the error and can't open any tables when working on the same machine the BE is stored on.

Whatever has changed only happened in the last couple of days. I was happily working on the FE on a networked PC linked to the BE, then copied the front end to the PC that has the BE stored locally on the C drive when the issue arose. It's something I've been doing for years without any problems until now. Very strange and not an easily found solution for (IMG:style_emoticons/default/iconfused.gif)

Hi Alan,

If you are getting the same error then maybe it is the computer that has the issue. Just to be certain, could you start up a DOS window and type the following?

NET SHARE

Then check to make sure you have a share named "C$." If you do, then try typing this next:

DIR \\PCName\C$\Amp\Data

If you get the same error, then I would say it's the computer.

Just my 2 cents... (IMG:style_emoticons/default/2cents.gif)

Hi DBG

NET SHARE confirms C$ and correctly lists the resource as C:\ - plus the other shares currently set up on this machine. However, DIR \\PCName\C$\Amp\Data produces

'The specified network name is no longer available'

which is somewhat odd as I can access the shared directories (including the BE data file) from any other PC on the network.

I'll see what Google turns up for that. Thanks for the suggestions (IMG:style_emoticons/default/wink.gif)

Okay... Good luck! (IMG:style_emoticons/default/thumbup.gif)

HI DBG

Your suggestion led me on the road to finding the cause of the issue..............it's my AV

I use Kaspersky (on all of my machines) which obviously included 'something' in one of it's recent updates that caused the problem. Disabling it resolved the problem, and re-enabling caused the issue again.

Strange though, as I have the same version of Kaspersky installed on two other machines, neither of whcih have the same problem. The differences are (for anyone else reading this) the OS. On XP and Win7 64 bit there is no problem, it only occurs on this Vista machine. It makes it even more strange that I can access the shares on this Vista machine from both the XP and Win 7 machines, but not by using a UNC path from the local machine.

Oh well, if not problem solved for the moment I at least know the cause. Thanks for pointing me to the culprit DBG (IMG:style_emoticons/default/wink.gif)

Now, off to the Kaspersky support forums...................

Hi Alan,

Congratulations! Glad to hear you are making good progress.

Cheers (IMG:style_emoticons/default/cheers.gif)