SQL2012 Compatability

Meeting place for R&R customers and clients to share tips and ideas. Post your questions, messages or problems here.
Post Reply
tcarter
Posts: 5
Joined: Tue Oct 10, 2017 12:44 pm

SQL2012 Compatability

Post by tcarter » Mon Aug 12, 2013 4:44 pm

__Some time back you provided this fix for outer joins and it successfully resolved my report at the time. However it doesn^t seem to work for an old report when there are two separate tables linked to the main table with asterisk outer joins. Does this mean a rewrite of the report?____The issue is probably with the syntax used for handling left outer joins. Are you using SQL Server?____If so, edit the file RSWSQL.INI and search for the SQL Server section:____;;;;;;;;;;;;;;;;;;;;;;__;;; ;;;__;;; SQL Server ;;;__;;; ;;;__;;;;;;;;;;;;;;;;;;;;;;____DataSourceDBMS = Microsoft SQL SERVER__DataSourceOuterJoinStyle = 1______*********************__Comment out the DataSourceOuterJoinStyle line by adding a semicolon at the beginning of the line.

User avatar
cstrasser
Posts: 155
Joined: Tue Oct 10, 2017 12:44 pm

=> RE: SQL2012 Compatability

Post by cstrasser » Tue Aug 27, 2013 6:00 pm

Yes. The old style join was *= and =* to indicate left / right OJ____This isn^t supported by SQL Server anymore and it needs to be re-written.
Chris Strasser
Liveware Publishing, Inc.
Work bigger.

tcarter
Posts: 5
Joined: Tue Oct 10, 2017 12:44 pm

==> RE: SQL2012 Compatability

Post by tcarter » Mon Sep 16, 2013 4:15 pm

>Yes. The old style join was *= and =* to indicate left / __>right OJ __>__>This isn^t supported by SQL Server anymore and it needs to __>be re-written. ____If the report is rewritten, does the latests version of R&R create correct outer joins for SQL2012 or does a "view" have to be created to feed the report

Post Reply