Changed to strongly typed dataset not reflected in Crystal Reports

I use Visual Studio .NET 2003 (C#) with embedded Crystal Reports.

I added a report to my solution which I based on a strongly typed dataset in the same solution.  After some initial work on the report, I added a field to the dataset.  However, I can not get Crystal Reports to refresh the field list - I have used the Verify Database option and this simply indicates that the database is up to date.  I have also switched on the "Discard data..." option.

The report works fine when passed the new dataset but I can not access the additional fields in the designer.  I have previously had this problem in another project and it resolved itself at some stage.
LVL 1
gpretoriusAsked:
Who is Participating?
 
pjapikseConnect With a Mentor Commented:
Delete the .cs generated by the data set generator, THEN regenerate the dataset from the schema.
0
 
Éric MoreauSenior .Net ConsultantCommented:
You need to re - "Generate the Dataset"
   -open your xsd
   -be sure that "generate dataset" is checked under the schema menu
  -You may need to save at this point



You need to re - "Set the location"
   -Open your report
   -right-click anywhere outside the report (in the grey zone)
   -Select database
   -select Set Location
   -In the "Replace with" list, open the "Project Data" node and the the "ADO.Net Datasets" node and find your schema there click on it and click the Replace button
   -now you can "Verify the database"

0
 
gpretoriusAuthor Commented:
I have tried your suggestion above already.  The dataset is set to generate.

I have tried replacing the data source as you indicate and it makes no difference.  
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
Éric MoreauSenior .Net ConsultantCommented:
You sometimes need close the project, re-open it, re-build it and only then you are able to set the location.
0
 
gpretoriusAuthor Commented:
I have tried:
Re-building everything
Closing everything down
Restarting my machine

0
 
Éric MoreauSenior .Net ConsultantCommented:
Are you sure that your xsd file is modified?
0
 
gpretoriusAuthor Commented:
Yes.  I have viewed the xsd file and it has the changes in it.  The additional fields are being populated and passed to the report at runtime.
0
 
Éric MoreauSenior .Net ConsultantCommented:
I had hard time with that in the past (more when I was using VS.Net 2002). I have ever been able to finally have my fields and some times after using the "Set Location" feature many time!

Sorry, I can't do much without having your problem on my PC!
0
 
TheAvengerCommented:
You need to refresh the database. Open the crystal reports editor and check the menus. Search for an option Verify database or something like this. You can try to right click outside the report, select Database->Verify database

Sorry for the inaccurate explanations but I have no installation in front of me. However I am sure this works (at least in most cases, don't forget it's Crystal....)
0
 
gpretoriusAuthor Commented:
>  select Database->Verify database
I have tried that already and it doesn't work
0
 
pjapikseCommented:
btw, you will have to toggle the "view all files" setting to see the .cs file.
0
 
gpretoriusAuthor Commented:
When I logged in today and did a Verify Database I was suddenly told that the database has been updated.

I then made a further change to the dataset which was not picked up, but deleting the .cs file, shutting down VS and on restart doing a Verify Database seems to have done the trick.
0
 
jrogovskyCommented:
This is one of the most frustrating issues in Crystal .Net. So much of Crystal just doesn't work properly or as expected.

The real solution is to "Log Off" the dataset using the "Database->Log On/Off Server..." dialog, then run the database verify.

No need to delete code behind files, run the custom tools, relaunch VS, or reboot.

It seems that Crystal caches the dataset schema and the verify tool only verifies against the cache, not the actual database. The Log Off feature ensures that the cache is cleared before a verify attempt, forcing the verify against the actual dataset.
0
All Courses

From novice to tech pro — start learning today.