Go the PUSH model. You'll be much happier.
Create a strong dataset.
Push the results of your stored procedure into the (typed/strong) dataset.
Create your report against the XSD of the typed dataset.
PUSH it to CR, instead of pulling data.
http://www.codeguru.com/csharp/.net/...cle.php/c13253
"Brad Pears" <bradp@truenorthloghomes.comwrote in message
news:O%23nfVz4OJHA.4772@TK2MSFTNGP03.phx.gbl...
>I have a vb.net 2005 project and have a Crystal report I have designed
>(using the built-in Crystal reports that came with .net 2005). The fields
>in my report are based on a stored procedure. I have now added a field to
>the database and have modifed the stored procedure to include this new
>field. However, when I go to my report and attempt to modify it to add this
>new field, the new field is not showing up in the list at all. It appears
>the only way to get it to show up is if I re-select and "Update" the
>datasource which completely removes all the detail fields from the report.
>This cannot be the way to do it. I cannot imagine any product where you
>would have to delete everything you have done to simply add one more
>field... Please tell me I am wrong.
>
Help!
>
Brad
>
