Jim Richmond
Top achievements
Rank 1
Rank 1
Jim Richmond
asked on 26 Apr 2007, 06:43 AM
I un-installed the Beta 2 and I have installed the latest version. Here are some issues I ran into:
1) When I 'Add Project Data Source', I select an ODBC database and I get "More restrictions were provided than the requested schema ('Tables') supports." Can't go any further, so I try some alternatives:
2) I then manually drag and drop an odbcConnection and configure a odbcDataAdapter similar to how I did with Beta2. Since I can't select the DataAdapter in the report's DataSource property, I generate a DataSet and select that. However, I get a 'Object reference not set to an instance of an object' (I can view the data). So to get it to work, I go into the designer code and manually set the DataSource property to the DataAdapter I created.
3) For testing, I tried to create a Business Object. I selected an assembly and class from another project and I can't seem to specify a method in the class or the needed parameters for the method. Is this supported?
4) Beta 2 reports are not supported in this version. I guess I can live with that as it was a beta. To fix, I just comment out some of the designer code that causes the issues, and the reports seems to run ok. Is this safe, or should I try to manually convert Beta 2 reports to this version via a copy and paste strategy?
5) This not an issue and probably too late to fix, but... It would be nice if SQL 2005 wasn't required for the Quick Starts (as I don't have it installed on my dev machine). An Access db would of been good.
Thanks, Jim
1) When I 'Add Project Data Source', I select an ODBC database and I get "More restrictions were provided than the requested schema ('Tables') supports." Can't go any further, so I try some alternatives:
2) I then manually drag and drop an odbcConnection and configure a odbcDataAdapter similar to how I did with Beta2. Since I can't select the DataAdapter in the report's DataSource property, I generate a DataSet and select that. However, I get a 'Object reference not set to an instance of an object' (I can view the data). So to get it to work, I go into the designer code and manually set the DataSource property to the DataAdapter I created.
3) For testing, I tried to create a Business Object. I selected an assembly and class from another project and I can't seem to specify a method in the class or the needed parameters for the method. Is this supported?
4) Beta 2 reports are not supported in this version. I guess I can live with that as it was a beta. To fix, I just comment out some of the designer code that causes the issues, and the reports seems to run ok. Is this safe, or should I try to manually convert Beta 2 reports to this version via a copy and paste strategy?
5) This not an issue and probably too late to fix, but... It would be nice if SQL 2005 wasn't required for the Quick Starts (as I don't have it installed on my dev machine). An Access db would of been good.
Thanks, Jim
1 Answer, 1 is accepted
0
Hi Jim Richmond,
We've already identified several problems with the Connect Data Source wizard when connecting to a data source through OLE DB and ODBC and already started working on them. The fix will be available with the first service pack. It seems that you've already have discovered the best way to workaround this issues - connect the data source manually.
Currently when connecting to a Business Object and instance of that object is created and passed to the Report.DataSource and in addition you can specify the property from this object to be used through the Report.DataMember. As of now you cannot use a method from the Business Object instance even this seems very reasonable.
After Beta 2 was released we had to change the Report API that caused your problems. If after you've commented/changed the code that the report designer has generated and your reports look like in Beta 2 it seems that you've successfully converted the reports. I'm sorry for the inconvenience and hope to have as little as possible changes in the report API.
As to the SQL requirement, we chose to go this way for one reason only - simplicity. We figure that most of our clients will have SQL installed which comes with the sample database Adventure Works. It is by no means required though - if you do not have it, our installer will install it for you. We may consider adding an Access database if this turns out to be a problem.
Regards,
Svetoslav
the telerik team
Instantly find answers to your questions at the new Telerik Support Center
We've already identified several problems with the Connect Data Source wizard when connecting to a data source through OLE DB and ODBC and already started working on them. The fix will be available with the first service pack. It seems that you've already have discovered the best way to workaround this issues - connect the data source manually.
Currently when connecting to a Business Object and instance of that object is created and passed to the Report.DataSource and in addition you can specify the property from this object to be used through the Report.DataMember. As of now you cannot use a method from the Business Object instance even this seems very reasonable.
After Beta 2 was released we had to change the Report API that caused your problems. If after you've commented/changed the code that the report designer has generated and your reports look like in Beta 2 it seems that you've successfully converted the reports. I'm sorry for the inconvenience and hope to have as little as possible changes in the report API.
As to the SQL requirement, we chose to go this way for one reason only - simplicity. We figure that most of our clients will have SQL installed which comes with the sample database Adventure Works. It is by no means required though - if you do not have it, our installer will install it for you. We may consider adding an Access database if this turns out to be a problem.
Regards,
Svetoslav
the telerik team
Instantly find answers to your questions at the new Telerik Support Center