Development Problems

Hi
Hope someone can help. I have a few legacy databases running on SQL Server
(developed before my time) which have a # in the name of the database.
I have been trying to write some reports that run off these databases
however whenever I attempt to preview or deploy the report I get an error
"Unable to access '/c'". I have narrowed it down to being something to do
with the # sign through moving things onto a test rig and removing the #
from the DB names and all is fine, however this is not really an option on
the live system.
My question is, does anyone know a way that I can get round this problem in
Reporting Services so I dont have to go through the process of modifying
about 20 different systems?
Thanks in advance.You could try placing the dbname within [], as in [pubs]
The brackets should take away any special meaning.
"Steven Clark" <sjc@.nospam.uk-support.net> wrote in message
news:hOOdnWLBBO7bvXHcRVnyrQ@.eclipse.net.uk...
> Hi
> Hope someone can help. I have a few legacy databases running on SQL
> Server (developed before my time) which have a # in the name of the
> database.
> I have been trying to write some reports that run off these databases
> however whenever I attempt to preview or deploy the report I get an error
> "Unable to access '/c'". I have narrowed it down to being something to do
> with the # sign through moving things onto a test rig and removing the #
> from the DB names and all is fine, however this is not really an option on
> the live system.
> My question is, does anyone know a way that I can get round this problem
> in Reporting Services so I dont have to go through the process of
> modifying about 20 different systems?
> Thanks in advance.
>