Recently I took a copy of an existing Crystal 11.5 report and tried to use ‘Set Datasource Location’ to move it from one table to another within the same database, e.g. from WIB01 to WIB01ALT, each having much the same fields.
The process seemed to have failed: it accepted ‘Update’ but still showed WIB01. But when I ran it, I found it had picked up the WIB01ALT data. Checking the SQL, I found it was in part
It was using the original table name as an alias. The fields continue to appear with the WIB01 table name, which is also used in the Field Explorer.
If I hadn’t tried running the report on the off-chance, I would have wasted some time needlessly re-creating the report from scratch. That’s why I have posted it as a tip. But it anyone understands why it works this way, I’d appreciate their input.
Madawc Williams (East Anglia, UK). Using Crystal 11.5 with SQL and Windows XP
The process seemed to have failed: it accepted ‘Update’ but still showed WIB01. But when I ran it, I found it had picked up the WIB01ALT data. Checking the SQL, I found it was in part
Code:
FROM ("TAR"."dbo"."CurrentMonth" "CurrentMonth" INNER JOIN "TAR"."dbo"."WIB01ALT" "WIB01"
If I hadn’t tried running the report on the off-chance, I would have wasted some time needlessly re-creating the report from scratch. That’s why I have posted it as a tip. But it anyone understands why it works this way, I’d appreciate their input.
Madawc Williams (East Anglia, UK). Using Crystal 11.5 with SQL and Windows XP