Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Conditional formats in Impromptu 6

Status
Not open for further replies.

AliG

Technical User
Sep 14, 2002
5
GB
I had an Impromptu 5 report which used a conditional format to hide rows, depending on a yes/no prompt. This worked just fine.

I converted the report to Impromptu 6 and it went crazy - lost columns and looked a real mess. I re-wrote the report in v6 assuming it was a conversion issue and I hit the same problem whenever I introduced my conditional format - has anyone else had this problem and more importantly does anyone know how to get around this?

Thanks for any help

Alison
 
Are you on Oracle? If so, the automatic translation of If-Then-Else statements into Decodes introduced in version 6 may be responsible. Try turning this off by adding the following under the
[Query Options] area of your Impromptu.ini


use automatic ORACLE Decode=0

Let me know if this fixes your problem.

Regards,

Dave Griffin
The Decision Support Group
Reporting Consulting with Cognos BI Tools
"Magic with Data"
[pc2]
 
I'm using Sybase but I'll try your suggestion anyway!

Can't get tot he datea till Monday but will let you know.


Thanks for prompt response.



Alison Gormley
 
Nope. If you are not on Oracle, the change to the ini shouldn't affect anything.

What does your SQL look like before the conditional format is added? and what is the syntax of the conditional format your are adding?

Regards,

Dave Griffin
The Decision Support Group
Reporting Consulting with Cognos BI Tools
"Magic with Data"
[pc2]
 
You've given me a big clue.


The SQL is "bitty" and made up of several selects - seems to be that way because I'm using a hotfile???? - I think that exlains why my conditional format is misbehaving.


Will look at it further tomorrow.



ALison
 
Generally you get several SQL selects when you are (pick 1 or both):

1) Doing outer joins beyond the capability of the underlying database.
2) Including summary data from multiple levels.

In each case, Impromptu runs the separate statements and 'stiches' the results together locally. In general you want to avoid separate statements, but in some cases it is unavoidable. If you are using a hotfile and outerjoins then it is unavoidable.

Regards,

Dave Griffin

The Decision Support Group
Reporting Consulting with Cognos BI Tools
"Magic with Data"
[pc2]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top