Linking Issues 2

[briank]

I posted a question a few days ago regarding how to link tables. After I
tried to impliment some answers I realized that I need some further guidance.
To reiterate, there is a fr and be mdb file at work. Both files are on the
network drive. I would like to copy these files and place on my laptop to do
work from home. The problem of course are the links.

One reply (suggestions by Albert Kallal) was to follow some code
(http://www.mvps.org/access/api/api0001.htm
http://www.mvps.org/access/tables/tbl0009.htm). His suggestions seems sound
but perhaps this is a little over my head. It seems that I need something a
little simplier. Is it possible to create two command buttons, one of which
will record the table's existing linked paths (i.e network paths) in a table
and relink these tables to my laptop's c: drive. Then I can do my database
modifications. Upon returning to the office, I can click on the second
button and the original network links would be restored. Since I will be the
only one in the office doing this I am wondering if this is a good approach?

 

[Jerry Whittle]

You want something simpler? How about an old DOS command to create a virtual
drive on your lap top! I haven't tested this in Vista yet but it does work in
XP.

Subst--Example

The following command creates a virtual drive Q for the path
C:\USER\BETTY\FORMS:

subst q: C:\user\betty\forms
Now, instead of typing the full path, you can reach this directory by typing
the letter of the virtual drive, followed by a colon, as in the following
example:
q:

If you are using long file names for the folders, use quotes.
subst q: "C:\My Databases"

To remove the virtual drive:
subst q: /d

You can also create more than one virtual drive at a time. I have two that I
load automatically on my home machine by putting the command lines in the
Autoexec.bat file.

Using subst you can mimic the network drives on your laptop. Then you won't
even need to relink the tables.

 

[Peter Hibbs]

Have a look at :-
http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE_ReLink.mdb'
which should be easier for you to implement as you only have to write
one line of code (and that is provided anyway).

HTH

Peter Hibbs.

 

[aaron.kempf]

ADP doesn't require you to maintain information in 2 different places.

Keep everything in one place- on the db server, where it belongs!

-Aaron

 

[briank]

Thanks Jerry. This approach was exactly what I was looking for. Simple.
Quick. Effective.