|Adding fields to database table causes error What is best practice? [message #659102]
||Thu, 10 March 2011 21:05
Registered: September 2010
I am trying to sort out the best way to solve a common situation where new fields are added to database tables.
I had a working report which had the dataset as
select * from table_a a
join table_b b on a.x=b.x
join table_c c on c.y=b.y
This lists all fields from table_a then all from table_b then all from table_c.
4 new fields were added to table_a and the report now gives the error
Column binding "contactrole" has referred to a data set column "contactrole" which does not exist.
1.What is the best method to fix the problem other than recreating the report?
2. should I not use select * ? my datasets get saved into a library for use in other reports.
I have tried refeshing the dataset and can see the new fields. I have then deleted one by one the fields the give this error whereever they are mentioned in the XML code, and then freshing the data bindings, but this is quite time consuming.
Is there a better way?
Powered by FUDForum
. Page generated in 0.01767 seconds