RE: [Firebird-odbc-devel] Crystal Reports registry patch

[Dmitry Y. <di...@us...>]

Hi Kevin,

> Most importantly -- it works!

Glad to hear it. A long while ago I had the same problem and this patch
helped me too.

> Being a novice with SQL, I still don't understand why the SQL
> is created
> using "alias names" (my term, probably very wrong) to the two tables
> (PATIENT1 instead of PATIENT and PROVIDER1 instead of
> PROVIDER).  It would
> seem more direct to simply reference the actual table names.
> What am I missing?

Crystal allows you to have a number of instances of any table in your
report. In this case aliases are the only way to avoid an ambiguity and
Crystal requires you to provide them for tables that are used more than
once. But internally Crystal doesn't care how many times every table appears
in your report and generate SQL aliases for all cases, even when you have
only one table. I agree it's stupid, but it's how it works.

> Thanks for your help!

You're welcome.


Cheers,
Dmitry