Greetings,
In an attempt to avoid hardcoding of server / database names in Reporting
Services Reports, I'm attempting to use a UDL for all of the Datasets.
I already have a datasource established, using the Data Link properties box,
which I then employ for each dataset, but I'm uncertain how I can change this
to use a UDL I created.
I've tried going into the data source for each data set I use and setting
the connection string to "File Name = R:\Datasource.udl" as well as tried:
Data Source = R:\Datasource.udl".
(Just a note, I use R:\ as the UDL is on a mapped network drive, if that
makes a difference)
The first, "File Name =" tells me it doesn't recognize the keywords "File
Name", the latter yields an error message (after a bit of a pause) telling me
"Could not connection to the database. Set and test the connection. Invalid
connection."
I know my UDL works as I use it in some DTS tools as a global variable to
insert into the code.
As of this point I'm a bit stumped, is it possible to use UDLs in reporting
services? Is there another, possibly better method than UDLs to achieve a
single-datasource point that many of the Microsoft tools we write in (such as
ASP.Net, Reporting Services, Data Transformation Services) could easily
reference?
Thanks kindly,
Bruce L-C [MVP] - 28 Feb 2006 21:18 GMT
I'm using ODBC and I have successfully done the following:
filedsn=C:\somedirectory\somename.dsn
I'm not familiar with udl but perhaps something similar would work for you.

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
> Greetings,
>
[quoted text clipped - 32 lines]
>
> Thanks kindly,