I have been using crystal reports alot lately and I enjoyed the results from it. One thing I don't like (only thing maybe) is the report designer in VS.NET.
Besides these considerations I had no problems with creating reports and adding them to my applications until yesterday. I was asked to create a complicated report, that resulted in designing subreports and importing them in the final report.
Here is what I usually do when I create a report:
1) create new report.
2) select an OLEDB SQL Server DataBase and the stored procedure that will give me the fields (old technology).
3) fill the report with fields and formulas.
4) save the report.
5) create an aspx file that creates a new instance of the report.
6) access the Database through ADO.NET and create a DataSet.
7) pass the DataSet as the DataSource of the Report.
8) export the Report to pdf file.
9) view the pdf file on the browser.
Now, creating the subreports with the same OLEDB access type (old technology) and trying to view the primary report on a network that refuses OLEDB connections I have a problem.
The way to solve it is to create those subreports through ADO.NET datasets in design mode. Right. I've tried and found no way since the crystal report designer, in the field window, under Database connections and in the ".NET DataSets" folder always gives me "no items found" and no way to create a dataset through ADO.NET (at least not from there).
Is there a way I can get this monkey off my back?
Thanks in advance... Daren J. Lahey
Just another computer guy...
Besides these considerations I had no problems with creating reports and adding them to my applications until yesterday. I was asked to create a complicated report, that resulted in designing subreports and importing them in the final report.
Here is what I usually do when I create a report:
1) create new report.
2) select an OLEDB SQL Server DataBase and the stored procedure that will give me the fields (old technology).
3) fill the report with fields and formulas.
4) save the report.
5) create an aspx file that creates a new instance of the report.
6) access the Database through ADO.NET and create a DataSet.
7) pass the DataSet as the DataSource of the Report.
8) export the Report to pdf file.
9) view the pdf file on the browser.
Now, creating the subreports with the same OLEDB access type (old technology) and trying to view the primary report on a network that refuses OLEDB connections I have a problem.
The way to solve it is to create those subreports through ADO.NET datasets in design mode. Right. I've tried and found no way since the crystal report designer, in the field window, under Database connections and in the ".NET DataSets" folder always gives me "no items found" and no way to create a dataset through ADO.NET (at least not from there).
Is there a way I can get this monkey off my back?
Thanks in advance... Daren J. Lahey
Just another computer guy...