If you are using stored procedures then this is easier. Either you modify
the stored procedure to alias the fields in which case you don't need to
have a view or you create a view that does the aliasing and then modify the
stored procedure. Either way, if the change is in the stored procedure you
don't have to make any change to the report.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
[quoted text, click to view] "DigitalVixen" <DigitalVixen@discussions.microsoft.com> wrote in message
news:31CA7232-F5DA-494B-A908-44ACA4C2BC76@microsoft.com...
> Thanks for the quick reply ;) Will this take care of the stored
> procedures
> as well as tables?
>
> "Bruce L-C [MVP]" wrote:
>
>> You could create a view which has the old names. Then edit the RDL to use
>> that instead of the current table name.
>>
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "DigitalVixen" <DigitalVixen@discussions.microsoft.com> wrote in message
>> news:358965CE-B1EA-44E0-92BB-753631D9105B@microsoft.com...
>> > Our software is going through some changes, in the next 6 months the
>> > database
>> > structure will have changed. I have written reports against the
>> > current
>> > structure, is there any "easier" way to update reports other than going
>> > in
>> > and giving an alias for the "new field name's"? I attempted this with
>> > the
>> > most simplistic report we have and even though the change to the query
>> > was
>> > just an alias it required me to change each field manually.
>> >
>> > Is there an easier way? Maybe edit the rdl direct?
>> >
>> > Thanks for any help.
>>
>>
>>
