I am using Crystal XI, MS SQL Server 2005 and MS Acess 2000.
I have data that I load monthly into a SQL Server 2005 database table. Before loading the monthly data I need to check for duplicates. To check for duplicates I created a Crystal Report that compares the primary key from the SQL Server table to the monthly data in an Access database table.
The above worked when I used Crystal 10. After upgrading to Crystal XI, the report crashes on execution. I recreated the report from scratch in Crystal XI, and continues to crash on execution.
- I've verified that the Crystal XI report can report off of the Access table, and can report off of the SQL table. It crashes after I link the tables.
- When I link the SQL table and the Access table in Crystal XI, the link automatically defaults to an inner join (which is what I want), but the link is a left outer join arrow, not a straight line.
- When I am in the Access Database, I can succussfully link the SQL table to the Access Database. When the tables are linked this way, I can create a Crystal XI report that only connects to the Access database. The Access connection lists both tables (the SQL table and Access table). The Crystal report correctly links the tables as an inner join represented by a straight line. The report correclty runs in Crystal.
There are security issues with the workaround, and I don't want to give users the ability to directly edit data in the SQL database tables.
Why won't Crystal XI run when linked to multiple data sources?
I have data that I load monthly into a SQL Server 2005 database table. Before loading the monthly data I need to check for duplicates. To check for duplicates I created a Crystal Report that compares the primary key from the SQL Server table to the monthly data in an Access database table.
The above worked when I used Crystal 10. After upgrading to Crystal XI, the report crashes on execution. I recreated the report from scratch in Crystal XI, and continues to crash on execution.
- I've verified that the Crystal XI report can report off of the Access table, and can report off of the SQL table. It crashes after I link the tables.
- When I link the SQL table and the Access table in Crystal XI, the link automatically defaults to an inner join (which is what I want), but the link is a left outer join arrow, not a straight line.
- When I am in the Access Database, I can succussfully link the SQL table to the Access Database. When the tables are linked this way, I can create a Crystal XI report that only connects to the Access database. The Access connection lists both tables (the SQL table and Access table). The Crystal report correctly links the tables as an inner join represented by a straight line. The report correclty runs in Crystal.
There are security issues with the workaround, and I don't want to give users the ability to directly edit data in the SQL database tables.
Why won't Crystal XI run when linked to multiple data sources?