Where 'c' <> 'c'
If I make changes to a report after working in the data tab, the where
clause will have "where 'c' <> 'c'" in it. This only happens when I
make changes to the data tab. I understand that this is how information
on the table and fields are retrieved, but it was never saving into the
report until the 10.08 release. Has anyone heard of this?
Thanks,
Nick Vaughan
clause will have "where 'c' <> 'c'" in it. This only happens when I
make changes to the data tab. I understand that this is how information
on the table and fields are retrieved, but it was never saving into the
report until the 10.08 release. Has anyone heard of this?
Thanks,
Nick Vaughan
This discussion has been closed.
Comments
We have not seen this bahavior before. Which database and connectivity are
you using? When you say that this information is being saved in the report,
do you mean when you view the template file as ascii text?
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
FibPlus. I can provide you with the files, but it is almost identical
to the daIBExpress. I am viewing the template in ascii. I can provide
you with the entire report if you like, but below is a snippet of the file.
SQLText.Strings = (
'SELECT ITEM_1.ITEM_ID, ITEM_1.PACKAGE_NO, '
' ITEM_1.DESCRIPTION, ITEM_1.TAXTABLE_ID, '
' ITEM_1.DEPARTMENT_ID, '
' ITEM_1.CLASSIFICATION_ID, '
' ITEM_SCHEMA_1.DESCRIPTION DESCRIPTION_2, '
' ITEM_1.ISTRACKED'
'FROM ITEM ITEM_1'
' INNER JOIN ITEM_SCHEMA ITEM_SCHEMA_1 ON '
' (ITEM_SCHEMA_1.MARKET_ID = ITEM_1.MARKET_ID)'
' AND (ITEM_SCHEMA_1.SEGMENT_ID = ITEM_1.SEGMENT_ID)'
' AND (ITEM_SCHEMA_1.GROUP_ID = ITEM_1.GROUP_ID)'
' AND (ITEM_SCHEMA_1.CLASS_ID = ITEM_1.CLASS_ID)'
'WHERE ('#39'c'#39' <> '#39'c'#39' )')
Thanks for the info. Which version of ReportBuilder did you upgrade from?
I did some tests with older versions and the same behavior occured. One
thing to note is that unless you are editing the sql code as text in DADE,
the TdaSQL object will not actually use the saved SQL in the template. It
will be re-generated every time the template is loaded. This means that
this SQL code is not actually ever used and will not affect your report when
printing.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
problem for us. Is there a way around this?
If possible, will you give me the steps I can take to reproduce an error?
I'm trying to track down where the "c <> c" is being added when you are
editing the sql as text. Typically when you decide to edit the sql as text,
the SQL object will take the SQL code you enter manually as-is. The only
time the where clause is processed is when you create and run your queries
through DADE.
Here were my steps...
1. Open a new report design and tab to DADE.
2. Create a new query with no search conditions, save the report to file as
ascii text. (The "c <> c" is present).
3. Re-open the same report design.
4. Edit the query as text and alter the SQL code. Re-save the report.
(the "c <> c" is not present).
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com