Link to home
Start Free TrialLog in
Avatar of Alaska Cowboy
Alaska CowboyFlag for United States of America

asked on

How to formulate a web link to a Word document on a Windows server

In a corporate environment, I want to create a web link to open a Word document. The document resides on a common drive on Windows file server.

So the document resides (for everyone) on R:\ftp\prod\edw\reports\cdr_2011_01_03.doc

My link works fine and the document opens but the actual link when hovering the mouse is

file:///R:/ftp/prod/edw/reports/cdr_2011_01_03.doc

This looks kind of cheesy with the "file:///" so can I do something to clean this up ? Even as is, I assume it will work for everyone because the "R:\" is common to all (including on Citrix)
ASKER CERTIFIED SOLUTION
Avatar of Tomarse111
Tomarse111
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Alaska Cowboy

ASKER

Tomarse, thanks.

I didn't indicate that the document is created on Unix, then I copy it to a Windows drive mounted on Unix. My webserver is just PC running Tomcat.

Amick, thanks, what does the auto refresh do ?

My website URL is http://xpc-120268/edw/dailyProcessingStatus.htm?filter=claim&DATE=02142011

I created a shortcut on my PC that to the "R:\" drive, but would my "EAR" file (from Rad-7) recognize this ?

Then my link would just be coded as reports/filename.doc which would be a shortcut to "R:\" drive.
You asked what the auto refresh does. It simply reloads a page after the number of seconds given in the content parameter. If a value is assigned to the url parameter, that is the url that is loaded.  The combination of the two enables the webpage creator to redirect a user elsewhere without their intervention.  One problem with this method of redirection is that it breaks the back button.  When users are redirected and then use the back button, they return to the page that originally redirected them.  Logically, they are redirected again thus are returned to the page they're trying to leave. A user can overcome this by using the history dropdown, but it is an annoyance that one should consider when deciding whether this is an appropriate method to use for redirection.

A client-side option that I didn't mention earlier is to use a frame.  This allows you to load the awkward URL without breaking the back button. Here's an example:
 
<html>
 <head>
 <title>REPORT</title>
 <frameset cols = "100%">
 <frame src="file:///R:/ftp/prod/edw/reports/cdr_2011_01_03.doc" />
 </frameset>
 </head>
 <body>
 </body>
 </html>
 

Open in new window

You should be aware that frames are deprecated in XHTML.

The server-side options are generally preferable, but the client-side options have their place and a knowledgeable webmaster will consider the benefits of each method before choosing a tool.
Amick, thanks for the follow-up explanation.