P
Paul Engel
The file protocol links (file://), according to Microsoft's KB article
330913, (http://support.microsoft.com/default.aspx?scid=kb;en-us;330913), is
no longer supported for security reasons.
I have an application I have written that sends a link to a user to a file
on their network that launches an application for them. Obviously, the
system is now obsolted by this change. Does ANYONE know of a work-around for
this? Is there a registry setting that can be changed so that my users can
regain the use of this mission-critical piece of our workflow? OR, does
anyone know of a clever idea on how I can do this using alternative
solutions?
I thought about emailing them a .bat file, but, of course, those get
filtered out...and opening that would create a greater threat than the one
Microsoft just eliminated with this change.
Any help would be appreciated.
Paul
330913, (http://support.microsoft.com/default.aspx?scid=kb;en-us;330913), is
no longer supported for security reasons.
I have an application I have written that sends a link to a user to a file
on their network that launches an application for them. Obviously, the
system is now obsolted by this change. Does ANYONE know of a work-around for
this? Is there a registry setting that can be changed so that my users can
regain the use of this mission-critical piece of our workflow? OR, does
anyone know of a clever idea on how I can do this using alternative
solutions?
I thought about emailing them a .bat file, but, of course, those get
filtered out...and opening that would create a greater threat than the one
Microsoft just eliminated with this change.
Any help would be appreciated.
Paul