Problem with Linked Tables

[MatMac]

Hi. I have just started experiencing an strange problem with linked tables, and would be greatful if you could let me know if you have experienced a similar thing.

Access version 2003. File structure 2000.

At work I run a multi-user database split into front and back ends. The back end resides on a shared drive. When I work from home on the database front end, I have two options: either access the shared drive using VPN (which is very slow), or instead create a front-end database file copy linked to a local back end on my hard drive (then re-link it to the shared drive when back at work). This latter strategy has all been working fine until recently.

So... At work I create a copy of my front end file, then using the linked table manager, link it to a back end on my C drive.

Then at home, with the same back file in the same location on my C drive there, the front end copy should open fine - it used to - but recently it has stopped working.

The strange thing is this - if I then connect to work using VPN, the "so-called local" database then opens fine, as if it is still trying to connect to the shared drive on my work intranet, hence requiring the VPN to be active. This despite the linked table manager reporting that the linked tables are local. Even stranger - once I have connected via VPN, once disconnected, the local database then closes and opens fine.

So - in summary - it seems that despite changing linked tables from a shared drive to a local drive, the front end still wants access to the shared drive, despite no reference to it in the front end database.

This is a recent problem. Through many front end file incarnations the above problem didn't occur. I have obviously asked myself what changes have been made before the error started. Well - all I have done is changed a few queries - have added a parameter query, modified a few forms - that sort of thing. Nothing I can think of to cause the above anomaly.

Strange, eh?? Any ideas?

Thanks

Mat Mackenzie

 

[odin1701]

Have you tried a compact/repair?

 

[rpadams]

Make your personal computer act like the linked directory. Done properly you won't have to re-link if that is where your problem lies.

Make a folder on your harddrive to copy the backend with the linked tables.

Example: c:\Datafolder\Application_be.mdb

From the DOS command line (or a simple .bat file) use the DOS subst command.

Example: subst f: c:\DataFolder where f is the path to the linked tables in your front end.

Done this way, your "links" remain and if you modify the front end (as I assume you are planning) you simply copy the new front end when done.

 

[MatMac]

Hi. Thanks for your responses.

Yes, sure - have tried compact/repair.

Subst Drive? Not sure if that will work, as my tables are not linked to a mapped drive - rather to an actual server address, commencing, e.g....

\\Fileserver1\xxxx.xxx.uk\folder\folder\folder... etc.

The reason I have to do this, is that my users end up with different drive letters assigned when they map a drive to this location, which doesn't work (subject of an earlier thread). Also, for some reason only my IT department knows access via VPN outside the intranet only works if I set it up this way.

Anyway, I would really like to get to the botom of why my original problem as above has just become apparent - the last thing I want is further problems down the line, when it would be impractical to backtrack to an earlier front end version that doesn't suffer from this problem.

So - if there's anyone out there who has experienced a similar thing and could shed some light - I would be very grateful.

Thanks - Mat M.

 

[Crowbar]

Hi. Thanks for your responses.

Yes, sure - have tried compact/repair.

Subst Drive? Not sure if that will work, as my tables are not linked to a mapped drive - rather to an actual server address, commencing, e.g....

\\Fileserver1\xxxx.xxx.uk\folder\folder\folder... etc.

The reason I have to do this, is that my users end up with different drive letters assigned when they map a drive to this location, which doesn't work (subject of an earlier thread). Also, for some reason only my IT department knows access via VPN outside the intranet only works if I set it up this way.

Anyway, I would really like to get to the botom of why my original problem as above has just become apparent - the last thing I want is further problems down the line, when it would be impractical to backtrack to an earlier front end version that doesn't suffer from this problem.

So - if there's anyone out there who has experienced a similar thing and could shed some light - I would be very grateful.

Thanks - Mat M.

I don't know if its any help, but remote desktop beats the heck out of VPN.
You just have to leave your computer on when you leave work. You can even shut it down remotely when you are finished.

 

[MatMac]

Our IT Dept does not permit remote desktop access into its intranet from outside.