By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,599 Members | 1,377 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,599 IT Pros & Developers. It's quick & easy.

problem with relative paths for references

P: n/a
I have a problem with setting references between library databases when
I move them to a different location. I thought that as long as the
relative path remained constant, the references would remain intact,
but this doesn't seem to be the case.

I have this sort of structure, with several Library databases in each
subdirectory:

DBDir+---LibSubDir1
|
+---LibSubDir2

References between libraries in LibSubDir1 cope fine when the DBDir and
contents are move to another location, but references from libraries in
LibSubdir1 to those in LibSubDir2 break. I thought that, since the
relative path is the same, this would be OK.

Any ideas why it isn't?

Cheers
Ian

Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Because it isn't <g>.

Try downloading the references wizard from
http://www.mvps.org/access/downloads/wzref.zip and look at the bit which
builds the RefLibPaths (modRefLibPaths) you'll need to change the
REG_APP_KEYS_PATH constant (change the 8.0 to whichever version of Access
you're using).

--
Terry Kreft

<ia******@yahoo.co.uk> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
I have a problem with setting references between library databases when
I move them to a different location. I thought that as long as the
relative path remained constant, the references would remain intact,
but this doesn't seem to be the case.

I have this sort of structure, with several Library databases in each
subdirectory:

DBDir+---LibSubDir1
|
+---LibSubDir2

References between libraries in LibSubDir1 cope fine when the DBDir and
contents are move to another location, but references from libraries in
LibSubdir1 to those in LibSubDir2 break. I thought that, since the
relative path is the same, this would be OK.

Any ideas why it isn't?

Cheers
Ian

Nov 13 '05 #2

P: n/a
Terry
Thanks for the References wizard. i was hoping to avoid making registry
entries, though.

What's confusing me is that the Access 2002 Developers Handbook (p1149)
says that if the absolute path of a reference doesn't work, Access then
tries the relative path. With further testing i've found that this has
worked...and then it hasn't...and then it has...and then... Obviously
there's something missing in what I'm doing, but I can't see what!

Ian

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.