ERROR - SQL Server 7, Reporting Services, and SQL 2000 Functions

I sincerely hope this is not the case...
Is it safe to assume that SQL Server Reporting Services cannot "talk" to SQL
Server 7 databases?
One of our developers is trying to run a simple test query against our SQL
Server 7 database; however, he is getting errors : "'DATABASEPROPERTYEX' is
not a recognized function name.". This is native to SQL 2000, though - so we
know why the error is occuring.
The question is why not use DATABASEPROPERTY for backwards compatibility?
How can we work around this limitation? We have tried modifying the provider
properties with no success; it appears this function call occurs behind the
scenes.
Thank you for your insight.
Elliot M. Rodriguez, MCSD
My .Net blog, with tips here and there:
http://derivedclass.europe.webmatrixhosting.netSQL7 did not support collations like SQL2000 does and the DATABASEPROPERTY
function does not have a Collation property. Having said that, this could
have been handled better :-)
You need to go to the "Data Options" tab of the "Dataset" dialog in
report designer for any datasets originating from SQL7
On the Data Options tab you will see that all settings contain "Auto".
Replace the Auto-settings with the following settings:
Collation = Latin1_General
Case sensitivity = false
Kanatype sensitivity = false
Width sensitivity = false
Accent sensitivity = true
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Elliot M. Rodriguez" <someemail> wrote in message
news:%23LY0TvJ9DHA.2756@.TK2MSFTNGP10.phx.gbl...
> I sincerely hope this is not the case...
> Is it safe to assume that SQL Server Reporting Services cannot "talk" to
SQL
> Server 7 databases?
> One of our developers is trying to run a simple test query against our SQL
> Server 7 database; however, he is getting errors : "'DATABASEPROPERTYEX'
is
> not a recognized function name.". This is native to SQL 2000, though - so
we
> know why the error is occuring.
> The question is why not use DATABASEPROPERTY for backwards compatibility?
> How can we work around this limitation? We have tried modifying the
provider
> properties with no success; it appears this function call occurs behind
the
> scenes.
> Thank you for your insight.
> --
> Elliot M. Rodriguez, MCSD
> My .Net blog, with tips here and there:
> http://derivedclass.europe.webmatrixhosting.net
>|||Jasper:
MANY thanks - works as described. I hope a KB comes of this; this is going
on my blog (with credit to you, of course :D)
Elliot M. Rodriguez, MCSD
My .Net blog, with tips here and there:
http://derivedclass.europe.webmatrixhosting.net
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:etPHbvL9DHA.2028@.TK2MSFTNGP10.phx.gbl...
> SQL7 did not support collations like SQL2000 does and the DATABASEPROPERTY
> function does not have a Collation property. Having said that, this could
> have been handled better :-)
> You need to go to the "Data Options" tab of the "Dataset" dialog in
> report designer for any datasets originating from SQL7
> On the Data Options tab you will see that all settings contain "Auto".
> Replace the Auto-settings with the following settings:
> Collation = Latin1_General
> Case sensitivity = false
> Kanatype sensitivity = false
> Width sensitivity = false
> Accent sensitivity = true
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "Elliot M. Rodriguez" <someemail> wrote in message
> news:%23LY0TvJ9DHA.2756@.TK2MSFTNGP10.phx.gbl...
> SQL
SQL
> is
so
> we
compatibility?
> provider
> the
>