ODBC Outer Join Problem in Imprompt

[phibic]

I have a catalog that I created using a ODBC connection to a SQL database where I have setup an outer join between two tables. For some reason, it is acting like a "inner" join.

I have recreated the same exact catalog but have it connecting to the database using a direct Microsoft SQL connection and the proper information is returned.

When I view the .iqd files generated from either type of connection, the SQL statement is the same.

I am currently running Impromptu version 6, does anyone know of a bug related to ODBC connections with outer joins in that version?

 

[DoubleD]

If you have the native driver, why are you creating an ODBC connection? It's only going to be slower.

I am what I am based on the decisions I have made.

DoubleD

 

[phibic]

I am using ODBC because of another application that I am tieing into and I need to have the "SQL statements" to be portable between the two using the same ODBC connection.

 

[DoubleD]

I know Cognos doesn't really support Imp 6, but have you checked with them regarding what the preferred ODBC connection method is?

Hope you find a solution.

I am what I am based on the decisions I have made.

DoubleD

 

[maripro]

The different behavior of the SQL outer join could be explained in Impromptu (Version 6) if the Governor prevents outer joins. Check the catalog setting in Impromptu menu - Catalog, User Profiles....and click the Governor tab. The 'outer joins' drop down box should say 'allow'.