Advantage v6.2

rbuser

We use a table named "CASE" with the end user designer. It is now a
reserved SQL
word with the latest Advantage version. We are now having problems
because the
SQL generated by the end user designer does not put double quotes around
the
table name.

Does RB 7.0 address this issue?

Thanks,

Ron Marx
Programmer
CFMC
--
Sender and recipient of this message agree that no contract or
modification of any contract
is created by this electronic communication and that the provisions of
the Uniform Electronic
Transactions Act do not apply to any electronic transmissions received
by or sent to
CFMC.

rbuser

Hi Ron,

change procedure 'TdaADSSession.BuildReservedWordList' in 'daAds.pas'.

regards,
Chris Ueberall;

rbuser

Does this solution apply to RB v6.03?

Thanks,

Ron Marx
Programmer
CFMC

rbuser

Hi Ron Marx,

the given solution applies to all version of 'daAds.pas' for any ReportBuilder version.
(Why asking? Add 'CASE' to the list, ready!)

regards,
Chris Ueberall;

rbuser

I recompiled unit, but still does not solve problem. The query designer gives error when
attempting to select fields because CASE is a reserved word. What is needed is for
double quotes to be put around the table name in the SQL. The SQL table alias is also
a problem because it uses the table name for the alias.

Unless there is another solution we will have to rename the table and go through all the
reports and rebuild them.

Thanks,

Ron Marx
PRogrammer
CFMC

rbuser

Ron,

I added 'CASE' to the list of reserved words:

// introduced in Advantage 6.2
FReservedWords.Add('CASE');

... and had no problem to use a table named 'Case.adt'.

I guess you did not change the right 'daAds.pas'.

regards,
Chris Ueberall;