Linking via UDC on LAN

[Rick]

I need some advice on how to accomplish this.

On my development PC I configured the path to my back-end tables so that it
conforms to the path on the server.
D:\Users Shared Folders\GENERAL\BF Programs Database\BF_data.mdb.
I need to link a table contained in the path:
D:\Users Shared Folders\GENERAL\SMH Programs Database\SMH_data.mdb.

I opened the BF_data.mdb and Linked to the "Clients" table in the
SMH_data.mdb then created the link to my FE-program.mdb from the
BF_data.link.

Works well on the development PC but when I move the FE and BE to the BF
Folder on the server the users do not get the proper table. It goes looking
for the file on the Users PC rather than on the server.

On the server I opened the BF_data.mdb, deleted the link the tried to re-add
it by going through Network Neighborhood so that it would create a UNC path:
\\smhserver\users\... etc. But the server (Win2003 SBS) still creates it as
a direct path (D:\\ etc).

How do I get the table linked so that the data comes from the smh-data and
doesn't look for it on the Users d:-drive?

Thanks for your advice.
Rick

 

[Guest]

In Days of Old when computers were Bold
and Windows had not been invented,
MS-DOS was the Boss
and we used SubSt so that this problem would be prevented.

With the Subst command you could create a virtual drive on your PC to mimic
a mapped drive on the server. For example you could make part of your hard
drive look like Drive Q: without repartitioning or anything drastic like
that. That way you develop the database on your PC with the virtual drive set
up like your customer's. Then when you put the FE into production, it's
already linked.

This works great if I'm working on a database a home and not on the
customer's network. If working on the network, you'll need to unmapped the
drive or risk messing with actual production data.

subst q: "D:\" will create a Q drive out of your D drive. So if you know
their normal mapped drive to the MDB file, you can simulate it on your
computer.

subst q: /d << removes the virtual drive.

You can automatically create the virual drive with a link in the
Autoexec.bat file or create a bat file to do it as necessary. subst can be a
little picky at times so look it up on the internet if you have problems.

 

[Rick]

Thank you very much Gerry. I will try this out.

In Days of Old when computers were Bold
and Windows had not been invented,
MS-DOS was the Boss
and we used SubSt so that this problem would be prevented.

With the Subst command you could create a virtual drive on your PC to
mimic
a mapped drive on the server. For example you could make part of your hard
drive look like Drive Q: without repartitioning or anything drastic like
that. That way you develop the database on your PC with the virtual drive
set
up like your customer's. Then when you put the FE into production, it's
already linked.

This works great if I'm working on a database a home and not on the
customer's network. If working on the network, you'll need to unmapped the
drive or risk messing with actual production data.

subst q: "D:\" will create a Q drive out of your D drive. So if you know
their normal mapped drive to the MDB file, you can simulate it on your
computer.

subst q: /d << removes the virtual drive.

You can automatically create the virual drive with a link in the
Autoexec.bat file or create a bat file to do it as necessary. subst can be
a
little picky at times so look it up on the internet if you have problems.