Ok.
We are devloping the reporting side of our system and I just want to find out the best way to do it all.
We are using VB 6, SQL Server 7
We originally had used the following set up.
-There is a view in the DB which has all the data required for the report.
-We set up an object in a data environment which looked at the view in the DB
-A Crystal Report Designer object in VB was created which used the data Environment object as it's data source
-The 'where' part of the select * from DataEnvironment.ViewObject was done via a form in VB.
-This was then passed to an instance of the report and displayed on screen in a form
We have also tried the following way:
-The report was set up in the same way but it's data source was set to RDO Active Data and it pointed to the view itself in the DB
-The entire select statement was created via the form in VB and then a recordset was opened using it
-This recordset is then passed to the report and opened
Both ways are quite effective but I feel the latter will be less resource hungry. Can anyone confirm which is actually the better way??
When we tried to edit the report created in the first instance and adapt it to work the second way (change the data source in the designer) it kept giving an error leading us to believe that once you have created a report it is hard/not possible to change where it gets it's data from without re-creating it from scratch.
Anyway, any advice/comments would be greatly apprciated.
--Simon
We are devloping the reporting side of our system and I just want to find out the best way to do it all.
We are using VB 6, SQL Server 7
We originally had used the following set up.
-There is a view in the DB which has all the data required for the report.
-We set up an object in a data environment which looked at the view in the DB
-A Crystal Report Designer object in VB was created which used the data Environment object as it's data source
-The 'where' part of the select * from DataEnvironment.ViewObject was done via a form in VB.
-This was then passed to an instance of the report and displayed on screen in a form
We have also tried the following way:
-The report was set up in the same way but it's data source was set to RDO Active Data and it pointed to the view itself in the DB
-The entire select statement was created via the form in VB and then a recordset was opened using it
-This recordset is then passed to the report and opened
Both ways are quite effective but I feel the latter will be less resource hungry. Can anyone confirm which is actually the better way??
When we tried to edit the report created in the first instance and adapt it to work the second way (change the data source in the designer) it kept giving an error leading us to believe that once you have created a report it is hard/not possible to change where it gets it's data from without re-creating it from scratch.
Anyway, any advice/comments would be greatly apprciated.
--Simon