Developing for 2000 and 2005

Hi,
What are our options for developing for 2000 and 2005 "at the same time" /
on one computer.
I upgraded my local sql2000 to sql2005 and installed Visual Studio 2005 side
by side with Visual Studio 2003. Now Visual Studio 2003 cannot open Sql2000
report server projects anymore and 2005 "complains" about upgrading the
report projects. For several customers we still need to develop Sql2000
reports while other customers request Sql2005 reports.
Please advise,
ErikYou need to keep the source for the RS 2000 reports separate from the RS
2005 reports. RS 2005 will still run 2000 reports. 2000 will not run 2005
reports. 2005 Report Designer converts 2000 reports when you try to modify
them in 2005.
I took a 2000 report (I have both report designers on my machine) and I
deployed it to RS 2005.
Although 2005 is supposed to run 2000 reports I have noticed some minor
problems. For instance, if I do this:
= "Myparam1 = " & Parameters!Myparam1.Label
It doesn't like the use of label. However, if I convert the report by
bringing it into the 2005 designer, convert, redeploy the error goes away.
My suggestion is to have two report servers. One for 2000 and one for 2005.
Having both designers on one machine is not a problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in message
news:eEZs$fB7FHA.3660@.TK2MSFTNGP09.phx.gbl...
> Hi,
> What are our options for developing for 2000 and 2005 "at the same time" /
> on one computer.
> I upgraded my local sql2000 to sql2005 and installed Visual Studio 2005
> side by side with Visual Studio 2003. Now Visual Studio 2003 cannot open
> Sql2000 report server projects anymore and 2005 "complains" about
> upgrading the report projects. For several customers we still need to
> develop Sql2000 reports while other customers request Sql2005 reports.
> Please advise,
> Erik
>|||Plausible.
The upgrade of Sql2000 to Sql2005 (developer editions) on my own machine
removed Sql 2000 Report Designed and installed Sql 2005 Report Designed. I
now reinstalled the Sql 2000 Report Designed (which I didn't think was
possible).
Thanks.
Erik
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:eQND1pE7FHA.268@.TK2MSFTNGP10.phx.gbl...
> You need to keep the source for the RS 2000 reports separate from the RS
> 2005 reports. RS 2005 will still run 2000 reports. 2000 will not run 2005
> reports. 2005 Report Designer converts 2000 reports when you try to modify
> them in 2005.
> I took a 2000 report (I have both report designers on my machine) and I
> deployed it to RS 2005.
> Although 2005 is supposed to run 2000 reports I have noticed some minor
> problems. For instance, if I do this:
> = "Myparam1 = " & Parameters!Myparam1.Label
> It doesn't like the use of label. However, if I convert the report by
> bringing it into the 2005 designer, convert, redeploy the error goes away.
> My suggestion is to have two report servers. One for 2000 and one for
> 2005. Having both designers on one machine is not a problem.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> message news:eEZs$fB7FHA.3660@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> What are our options for developing for 2000 and 2005 "at the same time"
>> / on one computer.
>> I upgraded my local sql2000 to sql2005 and installed Visual Studio 2005
>> side by side with Visual Studio 2003. Now Visual Studio 2003 cannot open
>> Sql2000 report server projects anymore and 2005 "complains" about
>> upgrading the report projects. For several customers we still need to
>> develop Sql2000 reports while other customers request Sql2005 reports.
>> Please advise,
>> Erik
>