Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Strange behavior with CR10
Message
De
15/07/2004 18:42:08
 
 
À
Tous
Information générale
Forum:
ASP.NET
Catégorie:
Rapports
Titre:
Strange behavior with CR10
Divers
Thread ID:
00924948
Message ID:
00924948
Vues:
77
I'm using C# with CR10, and am having a very strange problem. I'm able to isolate it, as follows...

1) I create a DataSet/XSD manually in VS.NET. Let's say it's 5 datatables, each with an ID and a description.

2) I create a report in CR10, and point to the XSD as the data source, and drop some of the columns on a report

3) I go back to VS.NET, and run the report, using the following...
myReport.Database.SetDataSource(MyDs.Tables[0],3,1);
myReport.Database.SetDataSource(MyDs.Tables[1],3,2);
...and so on...

Everything is fine...Until

4) I go back into the XSD designer, and manually add a couple of text/string columns...I regenerate the XSD, I re-open the report, delete the dataset definition and re-add it, and then go back to VS.NET and re-run my routine that generates the report

5) On the tables where I added columns, I get "Object reference not set to an instance of an object". If I remove the columns, the error goes away. The data for the new columns are not 'null', they are definitely populated.

Even if I create a brand new report with the modified XSD, I have the same problem.

Any ideas?

Thanks,
Kevin
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform