sql server reporting services:
You got me currious so I played around with it. This is pretty straight
forward. All you need to do is to assemble a string that ends up in the
format of \\servername\sharename\folder\subfolder
Try this out with a report that has a single textbox. Put in some text (like
Test Opening Shared Folder). Do a right mouse click on the textbox,
properties, advanced properties, navigation tab, jump to URL. Then put in
the following, including the equal sign:
= \\yourservername\yoursharename\foldername
Go to preview mode and click on it.
This expression can be based on anything you want, fields, report properties
etc. So you could have something like this in the jump to URL:
= "\\" & Parameters!Servername.Value & "\hardcodedsharename\" &
Fields!SomeFieldnameWithNameOfFolder.Value
The above shows you an expression with a combination of using Report
parameters, hardcoding a value and getting part of it from a field.
I hadn't thought about doing this but I can see how it could be useful.
When I add links like this I underline and make blue the text in the box so
the user knows they can click on it.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
[quoted text, click to view] "Buzz Busey" <don_busey@pfizer_com> wrote in message
news:uNNTounJFHA.2752@TK2MSFTNGP10.phx.gbl...
> Greetings,
>
> I have a database that includes as one of it's fields, links to folders on
a
> network share i.e. \\servername\SharedFolder\Subfolder When the user
clicks
> on the link, it opens that folder up. I would like to be able to do the
same
> functionality from a report. The only way I can see to do this is to
create
> a virtual directory on the web server pointing to this folder then saving
> all records in http:// format instead of just \\servername The advantage
of
> this is that I can just copy and paste the location out of windows
explorer
> instead of morphing it into the http:// format. Is there anyway to provide
> just a 'normal' link using the database field?
>
> Thanks!
>
> Buzz
>
> No trees were harmed in the generation of this message, but an enormous
> amount of electrons were terribly inconvenienced.
>
>