Guest_imported
New member
- Jan 1, 1970
- 0
An outside contractor used Crystal Report to export data to a SQL Server 7 database table via an ODBC connection in Visual Basic. The program worked fine, until we upgraded to CR7. We found that the field names before CR7 were GF_1, GF_2, etc., but are now GF1_{field1name), GF1_{field2name}. When this program tries to export 2 data fields: J.Job_Number (OR Group #1 Name) and Sum of J.Amount from the Group Footer 1 field, I get the message:
Column names in each table must be unique. Column name GF1_Job_Number in table 'XYZ' is specifed more than once.
These are the only 2 fields in the Design area of the Crystal Report. All areas except GF1 of the Crystal Report are suppressed. If I run this report with the DETAIL section unsuppressed, the detail records are exported with no problems.
For the few people who needed to run this program, we did not upgrade to the CR7 PDSODBC.DLL. But the problem did not go away in CR8, so now I'm trying to figure out what's going on. I can export to Excel and some other formats, but not ODBC. I tried putting Headings on the fields, but CR looks at the fieldnames. I also made sure there were no other tables in the SQL Server database that had the field name GF1_Job_Number. Any other ideas? OR is this 'by design' that Group Footers can't be exported to ODBC?!
Column names in each table must be unique. Column name GF1_Job_Number in table 'XYZ' is specifed more than once.
These are the only 2 fields in the Design area of the Crystal Report. All areas except GF1 of the Crystal Report are suppressed. If I run this report with the DETAIL section unsuppressed, the detail records are exported with no problems.
For the few people who needed to run this program, we did not upgrade to the CR7 PDSODBC.DLL. But the problem did not go away in CR8, so now I'm trying to figure out what's going on. I can export to Excel and some other formats, but not ODBC. I tried putting Headings on the fields, but CR looks at the fieldnames. I also made sure there were no other tables in the SQL Server database that had the field name GF1_Job_Number. Any other ideas? OR is this 'by design' that Group Footers can't be exported to ODBC?!