Okay does anyone else think it's silly that access stores the full path of
another MDB file when you link a table?

Is there anyway to circumvent that? So when I installed two MDB's with my
application it doesn't matter what the full path is?

"Kelly Cromwell" <cromwellink (AT) hotmail (DOT) com> wrote

Well, uh, no. How could Access/Jet know where your linked tables are located
if it did NOT store the full paths?

Umm, you could tell it to use another database in the same folder.

This concept doesn't really make much sense for databases you plan to
distribute now does it? you MUST install this mdb in C:\Temp. Oh yeah, and
your applications will not work over a network if your mdb's have linked
tables...

c'mon, i expect more from microsoft, there must be a work around.

Anyone?

I mean if VB can store relative path's why can't access?


"Scott McDaniel" <junk (AT) junk (DOT) com> wrote

Open up the front end of your database app. When you get the error
saying that the path for the database is not valid just click OK.
Next, go up to the Window menu in Access and click unhide. When the
unhide window comes up click on your database and the tables for your
database will appear showing that they are linked (but they really are
not). Delete all your tables. Then go up to the File menu in Access
and choose Get External Data -> Linked Tables. The Link window will
appear. Browse to find the database backend you are trying to link or
type the UNC in the filename box and then click the Link button. The
Link Tables box will appear. Choose all the tables you want to link
or just click select all and then click OK. This should link all your
tables to the backend database.



"Bradley" <bradley (AT) REMOVETHIScomcen (DOT) com.au> wrote