We are migrating from Cognos Impromptu to ReportNet. We want to have one framework-model for all reports (different packages are ok). The problem is that our database-model is complicated. We have a lot of loops and different joins in the database.
For example:
Loops:
Table A -> Table B
Table B -> Table C
Table c -> Table D
Table D -> Table A
different joins (so there are more possibilities to join from A to C):
Table A -> Table B
Table B -> Table C
TAble A -> Table F
Table F -> Table C
In reality there are more loops with different ways to join to tables... The weighting of joins (in impromptu) was no solution for us. So we had 4 different catalogs (with different joins and aliases) - but we are not satisfied with this solution (mainly because it is not user and maintainance-friendly).
Has anyone experiences with a complex database-model and making a proper framework-model for ReportNet? What is the best way to do this?
Thanks in advance,
Timida
For example:
Loops:
Table A -> Table B
Table B -> Table C
Table c -> Table D
Table D -> Table A
different joins (so there are more possibilities to join from A to C):
Table A -> Table B
Table B -> Table C
TAble A -> Table F
Table F -> Table C
In reality there are more loops with different ways to join to tables... The weighting of joins (in impromptu) was no solution for us. So we had 4 different catalogs (with different joins and aliases) - but we are not satisfied with this solution (mainly because it is not user and maintainance-friendly).
Has anyone experiences with a complex database-model and making a proper framework-model for ReportNet? What is the best way to do this?
Thanks in advance,
Timida