> Try entering the position of the PDF in your local file system as the base
> URL, then supplying relative path information in the Web link.

Okay, but that still isn't quite the "flexibility" I was looking for. I have all my PDF and HTML files in the
same directory. Can't I just specify a web link as just the file name (such as "file.htm)? And since it's in
the current directory, it finds the file no problem? Then it doesn't matter what drive or directory I move
things to; it always looks to the current directory and voila. I don't want to "taint" the location by entering
a base URL, 'cuase it will always want to look there. Are you saying that Adobe doesn't support this basic
approach to looking in the current directory by default?

P.S. I won't be moving the files to a web server; they'll remain as files on the local hard drive.

>
> You are not alone in expecting a more seamless integration with HTML and other
> data types common to the Web and the desktop.
>
> As currently implemented, only "Go to view" links between PDFs can survive the
> transition from a local file system to a Web server or vice versa. All others
> go awry - "open file" "Web" and "movie" links. This is especially unfortunate
> given that the next Windows release will largely erase the distinction between
> local and Web files. Can you say intranet?
>
> I hope Adobe will generalize linking behavior for all data types and major
> network protocols. Maybe all links should behave as "open file" links do now,
> but with Reader/Exchange synthesizing an http request from a base URL and
> relative path info if the target is not found locally. They could also develop
> a simple means of referencing a given PDF page/view from HTML and submit it to
> the W3C. Or just get Netscape to implement one before their window of
> opportunity to define HTML closes. :^)
>
> ________________________________
> Todd Fahrner
> http://www.verso.com
> mailto:fahrner@pobox.com