Last post Oct 12, 2010 12:07 PM by apauls
Oct 07, 2010 11:58 AM|bonzo_bcn|LINK
I am creating my first report.
I have selected the tables using the wizard, but for some reason CR doesn't display all the fields in the tables, so there are some tables in Field Explorer that lack some fields. The fields that aren't shown are both int, and varchar, some of them allow
nulls and some of them don't, I can't seem to find a pattern as why some fields aren't loaded into Field Explorer.
I've searched this forum all day but nobody seems to have this problem.
Oct 07, 2010 01:10 PM|sansan|LINK
It seems like you have selected specific columns from the table. When you select a table, click either finish to get all columns or select all columns in the next screen.
Oct 07, 2010 01:23 PM|bonzo_bcn|LINK
No, that's not the case, I just tried it and still the same problem.
I also created a blank report, then added a table with Database Expert and still the same problem, only 3 out of 9 fields are loaded.
Also when I click on 'Browse data' of any field, no data is displayed allthough the table has records.
I'm attaching an image with the sql structure and what is displayed in visual studio.
Oct 08, 2010 03:35 AM|bonzo_bcn|LINK
Just in case anyone faces the same problem I figured out why.
The fields that are not displayed by CR are the ones that in my DB.designer.cs file are defined as type System.Nullable. I guess I'll have to find a turnaround as this file is generated automatically.
Oct 12, 2010 12:07 PM|apauls|LINK
If I understand you correctly, the column headings are showing up, but there is no data for them - correct?
If so, I had the same problem. If a column has all null values for the first 10 records, Crystal assumes that all the subsequent fields are then null values as well. I was working with an Excel document for a database at the time, so I simply inserted
a "test" profile as the first record and made sure it had values in every column. Problem solved.
I'm sure you could adapt this somehow for your sql - it depends on what order the records are being pulled out of the database. If you can somehow tell it to pull a "test" record first, you can solve the problem.