Dlookup for changing drives/paths

  • Thread starter Thread starter Rick
  • Start date Start date
R

Rick

Hi,
I have an Access 2k app that I will be deploying to
multiple workstations. Most of the tables are linked from
a local back end file which is located in the C: drive.
If I deploy the app to a user who needs to put the
application (including the backend) in a different drive
(let's say the H: drive) - they have to run the linked
table manager to re-establish the table links. I now use
dlookup behind a form to allow users to switch to a
different drive by entering the drive letter into a field
in an underlying table. This works great for most of my
coded procedures. But I'm not sure that this will work
for linking tables, since I would have to delete the
tables, which have relationships, before relinking them by
using the transferdatabase method. Is there an easier way
to re-establish table links - from a form or by another
means - that would work for my scenario? Thanks for any
help,
-Rick
 
The relationships are in the BACKEND mdb file.
The linked tables in the FRONTEND file don't have relationships.

So you can delete them if you want.

I used to put the backend on a server and then set up shares.
Then I linked once and typed a UNC name like:
\\MyServer\MyShare\MyFile.mdb

This way the link was valid for all users.
 
Thanks. If I can delete the relationships entirely in
the frontend, I should be able to use dlookup with
transferdatabase to do it. I too use UNC paths for
backends located on servers, but in this particular app,
there is no server, all tables are local and text files
are transfered out to frontends from a main frame
system. Other thoughts? Thank again,
-Rick
 
It doesn't matter whether the attached tables are on a server, or on your
hard drive. The point is that the relationships are always in the database
where the tables exist, not in the database that's linked to them. If you
have relationships in the front-end database, they aren't going to do
anything.
 
Back
Top