dpatfield66
Well-known member
- Joined
- Apr 6, 2006
- Messages
- 136
- Programming Experience
- 5-10
There has got to be a simple answer to this.
My boss wants me to use the reporting functionality within Studio.
The .rdlc files. He doesn't want me to use SQL reporting services, nor does he want Crystal.
So, I can create an .rdlc file but I can't get it to take a datasource OTHER than the one created by the DataSet.xsd when I use the wizard.
Let me see if I can explain this:
1. I have tables in SQL from a DB called Forms
2. When I add them to .NET/Studio, I get a FormsDataSet.xsd with basically my tables.
3. I can create customized fills and inserts, etc...but if I EVER make changes to my Database in SQL, I have to recreate the FormsDataSet.xsd, which erases all my custom queries.
4. To resolve this, I created 3 classes for each of my 3 tables. Within these tables are custom queries. So now, if I ever need to recreate the FormsDataSet.xsd, there's no problem.
----------------------------------------------------
But the report objects (.rdlc) keep wanting to point to the FormsDataSet.xsd and NOT my class queries (methods, whatever). The only thing available in the design view of the .xsd file is a basic FILL statement. All I want to do is one of the following:
1. Create Queries in my classes that can be used as source data for the report.
2. Create stored procedures or views from SQL that I can use as the data source for my reports. If I do this, I'm not sure how to include parameters...
Ex: SELECT * FROM OBAdmit WHERE AdmitID = '@AdmitID' Because AdmitID is an integer, SQL is giving me an error. If I use this process with string fields (varchar), I'm ok, or at least i THINK I'm ok.
SUMMARY: How can I get these darned reports to simply take some query as their source data, end of story. Without all this gobbledegook???????
My boss wants me to use the reporting functionality within Studio.
The .rdlc files. He doesn't want me to use SQL reporting services, nor does he want Crystal.
So, I can create an .rdlc file but I can't get it to take a datasource OTHER than the one created by the DataSet.xsd when I use the wizard.
Let me see if I can explain this:
1. I have tables in SQL from a DB called Forms
2. When I add them to .NET/Studio, I get a FormsDataSet.xsd with basically my tables.
3. I can create customized fills and inserts, etc...but if I EVER make changes to my Database in SQL, I have to recreate the FormsDataSet.xsd, which erases all my custom queries.
4. To resolve this, I created 3 classes for each of my 3 tables. Within these tables are custom queries. So now, if I ever need to recreate the FormsDataSet.xsd, there's no problem.
----------------------------------------------------
But the report objects (.rdlc) keep wanting to point to the FormsDataSet.xsd and NOT my class queries (methods, whatever). The only thing available in the design view of the .xsd file is a basic FILL statement. All I want to do is one of the following:
1. Create Queries in my classes that can be used as source data for the report.
2. Create stored procedures or views from SQL that I can use as the data source for my reports. If I do this, I'm not sure how to include parameters...
Ex: SELECT * FROM OBAdmit WHERE AdmitID = '@AdmitID' Because AdmitID is an integer, SQL is giving me an error. If I use this process with string fields (varchar), I'm ok, or at least i THINK I'm ok.
SUMMARY: How can I get these darned reports to simply take some query as their source data, end of story. Without all this gobbledegook???????
