Currently, when a .doc file or a .ppt file is placed as a hyperlink, clicking on the hyperlink will automatically open the file. Is there a way to force it to prompt the question of whether the user wants to open it or to save it to disk.

The method can be via HTML or JavaScript.

Note that I am doing this as a server administrator, so posts telling me to set my personal settings is akin to expecting me to demand all my users to set their OS the way I want them to. I need a more concrete solution.

Cheers for any solutions. [img]smile.gif[/img]

Right click and choose >Save target as...<.

[ 10-21-2003, 08:11 AM: Message edited by: Jorath Calar ]

I think Dundee is looking for a way to activate the "save as.." function with a left-click on a hyperlink. Else there wouldn't be a problem. ;)

Dundee, why do you need this? Not that I can help in any way, I'm sorry to say. I know next to nothing about HTML or Javascript :(

Unfortunately, how the browser interprets the file is up to the browser itself.

Workaround - provide the documents in .zip format. Its standard enough that nobody should have much trouble with it and it'll save you bandwidth.

Ironically, this is the current way I am doing it, but my Major wants me to somehow magically armtwist all browsers into prompting the question. It's like telling a dog to not chase its' tail I tell ya. [img]tongue.gif[/img]

Zipping them also presents a new set of problems. It takes up a loooot of space. I am essentially almost doubling my space usage.

So is it confirmed then? It's impossible?

Tell you major he is asking the wrong guy... he should talk to Bill Gates... [img]smile.gif[/img]

The problem is that browsers are configured to open particular data types with particular applications. That's why changing the name to an unknown type is a good idea as the browser won't know what to do with it so will always offer the save as option. I don't know of any way of forcing the file to be able to be to saved since javascript is only for client-side scripting and servers don't usually have permission to write to clients anyway, so there'd be no point in having such a method.

There is no way of doing. I just got done doing a month's worth of research for a client trying to find a way. Finally was able to weasel an admission from an MS tech that it is controlled client-side and there is nothing you can do server-side to force it.

As I thought! Makes sense as I said in my previous post...